Clarify rules for copies vs views when indexing#512
Merged
shoyer merged 2 commits intopydata:masterfrom Aug 20, 2015
Merged
Conversation
Member
Author
|
@jhamman any thoughts? |
Member
There was a problem hiding this comment.
for the last point, an example showing both behaviors may be helpful.
Member
Author
There was a problem hiding this comment.
unfortunately, the distinction here is pretty complex and I'm not even sure I understand it fully...
Member
|
I made a few comments. I think you'll have to sort out the merge conflicts coming from #507. |
shoyer
force-pushed
the
slice-indexing-never-copies
branch
from
bb51a8e to
5814a12
Compare
Member
Author
|
Revised and rebased. |
Member
|
I'm not able to build the docs from where I am but from what I can tell, this looks good. |
shoyer
added a commit
that referenced
this pull request
Aug 20, 2015
Clarify rules for copies vs views when indexing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This mostly reorganizes/updates the indexing documentation.
It also catches an edge case where a slice based indexer could be converted silently into array indexer. This is a strange edge case involving unsorted or duplicate indexes that arguably pandas shouldn't allow anyways.