Skip to content

CLN: Change assert_(a [not] in b) to specialized forms #6395

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

Merged
merged 1 commit into from
Feb 22, 2014
Merged

CLN: Change assert_(a [not] in b) to specialized forms #6395

merged 1 commit into from
Feb 22, 2014

Conversation

bwignall
Copy link
Contributor

Work on #6175. Changes instances of assert_(a [not] in b) to specialized assert[Not]In(a, b).

Work on #6175. Changes instances of assert_(a [not] in b) to specialized assert[Not]In(a, b).
@bwignall
Copy link
Contributor Author

Busy week; does this need to be rebased?

Is there any easy way on this screen to tell if a PR has conflicts? When creating a PR there is a prominent icon, but I am not seeing anything obvious now that the PR has been created.

jreback added a commit that referenced this pull request Feb 22, 2014
CLN: Change assert_(a [not] in b) to specialized forms
@jreback jreback merged commit 9564ead into pandas-dev:master Feb 22, 2014
@jreback
Copy link
Contributor

jreback commented Feb 22, 2014

If on a PR is say 'this PR can be automatically merged' then no conflicts

@bwignall bwignall deleted the assert_6175_innotin branch February 22, 2014 15:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants