Skip to content
This repository has been archived by the owner on Nov 10, 2024. It is now read-only.

Same function - two outputs! #lookup_users act differently - Why? #273

Closed
Waqasejaz opened this issue Jul 14, 2018 · 1 comment
Closed
Labels

Comments

@Waqasejaz
Copy link

Query - Unexpected Behavior

Thanks for the fantastic package and making life a lot easier. I have been using the package for some time, and suddenly I felt the same function behaves differently, and because I could not find the solution or any clue so decided to ask.

The screenshot below indicates the output of "lookup_users" that I used a month ago, it was a bunch of users from my sample and as you can see the output looks visibly different from the same command today. Initially, I could get info like "location", Name" etc, now I don't get such an info.

screen shot 2018-07-14 at 7 28 56 pm

Using the same command gives me this input now which primarily less informative with tons of NAs and no location, name follower's count etc. The new output gives me this:

screen shot 2018-07-14 at 7 29 23 pm

So, the question is have you with your new upgrade changed it? I need to know this as I will have to cite the reason for the alteration in the paper. Or is this something I am not doing right?

@llrs
Copy link
Collaborator

llrs commented Feb 15, 2021

Probably this was a breaking change on an upgrade... closing this as it is unlikely to receive ever an answer.

@llrs llrs closed this as completed Feb 15, 2021
@llrs llrs added the question label Feb 15, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants