-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
TST: Eliminating references to pandas.util.testing.choice #12490
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Want to remove pandas.util.testing.choice. First eliminating all references to it. Doing this in more than one commit as there are a lot of them. #12386
Want to remove pandas.util.testing.choice. First eliminating all references to it. Doing this in more than one commit as there are a lot of them. #12386
Removed pandas.util.testing.choice. Also eliminated all references to it. #12386
Removed pandas.util.testing.choice. Also eliminated all references to it. #12386
gr8! can you add a whatsnew (even though this is a testing function, technically was in 'public' space, you can put in bug fixes). |
Added entry to whatsnew. #12386
I'm having trouble squashing. When I do the following:
I see a bunch of other people's commits also, not just mine. Perhaps this is because I didn't branch off my fork, but worked on it directly? |
Removed pandas.util.testing.choice method. Replaced all references to it with calls to np.random.choice(). Added entry to whatsnew.
Yeah, it's typically best to work off feature branches. What happens if you |
I'll make a new pull request from another branch tomorrow evening (and close this one afterwards). Thanks for the suggestion. |
Or I guess I'll close this one first to eliminate confusion. Anyway, I'll work on it tomorrow night. |
you don't need a new PR. just rebase and force push. |
fix anything, then force push ( |
git diff upstream/master | flake8 --diff
Want to remove pandas.util.testing.choice. First eliminating all
references to it. Doing this in more than one commit as there are a lot
of them.
#12386