Skip to content
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

BUG: No affect both index and column(GH 13522) #14005

Merged
merged 1 commit into from
Aug 17, 2016

Conversation

conquistador1492
Copy link
Contributor

@codecov-io
Copy link

codecov-io commented Aug 15, 2016

Current coverage is 85.29% (diff: 100%)

Merging #14005 into master will increase coverage by <.01%

@@             master     #14005   diff @@
==========================================
  Files           139        139          
  Lines         50245      50247     +2   
  Methods           0          0          
  Messages          0          0          
  Branches          0          0          
==========================================
+ Hits          42857      42859     +2   
  Misses         7388       7388          
  Partials          0          0          

Powered by Codecov. Last update 7c0b742...6dfd2bc

@jreback jreback added Bug Indexing Related to indexing on series/frames, not to indexes themselves Reshaping Concat, Merge/Join, Stack/Unstack, Explode labels Aug 15, 2016
@jreback
Copy link
Contributor

jreback commented Aug 15, 2016

can you run an asv and see if anything changed signficantly. lgtm otherwise.

@@ -861,6 +861,7 @@ Bug Fixes
- Bug in ``io.json.json_normalize()``, where non-ascii keys raised an exception (:issue:`13213`)
- Bug when passing a not-default-indexed ``Series`` as ``xerr`` or ``yerr`` in ``.plot()`` (:issue:`11858`)
- Bug in area plot draws legend incorrectly if subplot is enabled or legend is moved after plot (matplotlib 1.5.0 is required to draw area plot legend properly) (issue:`9161`, :issue:`13544`)
- Bug in ``DataFrame``, assigning a string index as a column once can make further assignments affect both index and column (:issue:`13522`)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe something like: Bug in DataFrame assignment with an object-dtyped Index where the resultant column is mutable to the original object.

@conquistador1492
Copy link
Contributor Author

@jreback all benchmarks not significantly changed beside groupby.groupby_frame_singlekey_integer.time_sum. It ranges from 1 to 1.2

@jreback jreback added this to the 0.19.0 milestone Aug 17, 2016
@jreback jreback merged commit 15e9401 into pandas-dev:master Aug 17, 2016
@jreback
Copy link
Contributor

jreback commented Aug 17, 2016

thanks!

@conquistador1492 conquistador1492 deleted the issue_13522 branch August 18, 2016 08:49
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 Reshaping Concat, Merge/Join, Stack/Unstack, Explode
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Assigning a string index as a column once can make further assignments affect both index and column.
3 participants