Skip to content

BUG: fix repring of nat multiindex and fix neg indexing in datetimeindex #7410

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
Jun 9, 2014
Merged

BUG: fix repring of nat multiindex and fix neg indexing in datetimeindex #7410

merged 1 commit into from
Jun 9, 2014

Conversation

cpcloud
Copy link
Member

@cpcloud cpcloud commented Jun 9, 2014

closes #7406, #7408, #7409

@cpcloud cpcloud self-assigned this Jun 9, 2014
@cpcloud cpcloud added this to the 0.14.1 milestone Jun 9, 2014
Fix neg indexers in datetimeindex
@cpcloud
Copy link
Member Author

cpcloud commented Jun 9, 2014

@jreback good 2 go?

@jreback
Copy link
Contributor

jreback commented Jun 9, 2014

3x issues +1!

cpcloud added a commit that referenced this pull request Jun 9, 2014
BUG: fix repring of nat multiindex and fix neg indexing in datetimeindex
@cpcloud cpcloud merged commit 6c7c5b7 into pandas-dev:master Jun 9, 2014
@cpcloud cpcloud deleted the nat-index-first-take-7406 branch June 9, 2014 22:34
@hayd
Copy link
Contributor

hayd commented Jun 9, 2014

Neat!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Indexing Related to indexing on series/frames, not to indexes themselves Output-Formatting __repr__ of pandas objects, to_string
Projects
None yet
Development

Successfully merging this pull request may close these issues.

repr of MultiIndexed frame with NaT as the first element of level 0 of the index raises during repr
3 participants