Skip to content

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

Closed
wants to merge 7 commits into from
Closed

TST: Eliminating references to pandas.util.testing.choice #12490

wants to merge 7 commits into from

Conversation

paul-reiners
Copy link
Contributor

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
@jreback jreback added the Clean label Feb 28, 2016
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
@jreback
Copy link
Contributor

jreback commented Feb 29, 2016

gr8!

can you add a whatsnew (even though this is a testing function, technically was in 'public' space, you can put in bug fixes).
squash as well. ping when green.

@paul-reiners
Copy link
Contributor Author

I'm having trouble squashing. When I do the following:

git rebase -i HEAD~5

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.
@TomAugspurger
Copy link
Contributor

Yeah, it's typically best to work off feature branches.

What happens if you git rebase -i upstream/master and put all your commits at the end by moving those lines down, and the squash? Otherwise we can just make a new pull request from another branch (git co -b remove-tm-choice)

@paul-reiners
Copy link
Contributor Author

I'll make a new pull request from another branch tomorrow evening (and close this one afterwards). Thanks for the suggestion.

@paul-reiners
Copy link
Contributor Author

Or I guess I'll close this one first to eliminate confusion. Anyway, I'll work on it tomorrow night.

@jreback
Copy link
Contributor

jreback commented Mar 1, 2016

you don't need a new PR. just rebase and force push.

@jreback
Copy link
Contributor

jreback commented Mar 1, 2016

git checkout master
git pull
git checkout <thisbranch>
git pull --rebase master

fix anything, then force push (-f)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CLN: remove pandas.util.testing.choice
3 participants