Skip to content

Conversation

cpcloud
Copy link
Member

@cpcloud cpcloud commented Jun 6, 2014

closes #7376

@cpcloud cpcloud added the Bug label Jun 6, 2014
@cpcloud cpcloud added this to the 0.14.1 milestone Jun 6, 2014
@cpcloud cpcloud self-assigned this Jun 6, 2014
@cpcloud
Copy link
Member Author

cpcloud commented Jun 6, 2014

@jreback @jseabold comments? passes except a random failure on 2.7

@jreback
Copy link
Contributor

jreback commented Jun 6, 2014

looks ok

@jseabold
Copy link
Contributor

jseabold commented Jun 6, 2014

I'm not sure I really understand the implications of the change, but looks harmless enough?

Should probably go in the release notes if for some reason someone was relying on the TypeError being raised. The rest of the magic methods still raise a TypeError, though I doubt it's worth worrying about consistency here? I can't see much of a reason for it.

@cpcloud
Copy link
Member Author

cpcloud commented Jun 6, 2014

yep there will be a doc blurb in v0.14.1.txt

cpcloud added a commit that referenced this pull request Jun 6, 2014
@cpcloud cpcloud merged commit ef9b818 into pandas-dev:master Jun 6, 2014
@cpcloud cpcloud deleted the replace-no-match-7376 branch June 7, 2014 17:01
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.

bug in replace?
3 participants