Skip to content

reset_index fails if level and drop are both specified #1957

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.

Sign up for GitHub

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

Jump to bottom
Closed
changhiskhan opened this issue Sep 24, 2012 · 0 comments
Closed

reset_index fails if level and drop are both specified #1957

changhiskhan opened this issue Sep 24, 2012 · 0 comments
Labels
Bug Indexing Related to indexing on series/frames, not to indexes themselves
Milestone
0.9

Comments

@changhiskhan
Copy link
Contributor

If drop is specified then level looks like it's ignored and all levels are reset
changhiskhan added a commit that referenced this issue Sep 24, 2012
@changhiskhan
BUG: DataFrame.reset_index failure if both drop and level are present #…
c78d5c5 
…1957
yarikoptic added a commit to neurodebian/pandas that referenced this issue Sep 27, 2012
@yarikoptic
Merge commit 'v0.9.0rc1-14-g1a4f041' into debian
11a6c02 
* commit 'v0.9.0rc1-14-g1a4f041':
  DOC: add release notes to whatsnew
  Release notes and addition to test case for tzlocal
  BUG: errors when tz is tzlocal
  Add skip_footer to ExcelFile.parse and alias skipfooter/skip_footer
  revert skip_footer API change. use nrows instead
  ENH: between_time across midnight pandas-dev#1871
  BUG: DataFrame.reset_index failure if both drop and level are present pandas-dev#1957
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug Indexing Related to indexing on series/frames, not to indexes themselves
Projects
None yet
Milestone
0.9
Development

No branches or pull requests
1 participant
@changhiskhan