-
-
Notifications
You must be signed in to change notification settings - Fork 18.6k
DOC: ref / val caveat, point at pandas methods #3399
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
DOC: ref / val caveat, point at pandas methods #3399
Conversation
looks good, I would add the notes using the rst like this
|
@jreback thanks for your pointer. Just pushed another iteration over the text with .rst directives. |
next tip:rebase these to a single commit (you don't always want to do this, but in this case since
use the commit 1 previous to your first commit then either squash (s) / fixup (f) the commits to form a bigger one (s preservers the commit message, f does not) then
will replace all of these commits with a new one.... (w/o the f it just appends new commits) |
@jreback here we go ;-) |
@dengemann , can you wrap that text to match the rest of the document? |
Yeah, I forgot about about that, sorry. Hold on. On Sat, Apr 20, 2013 at 11:54 AM, y-p notifications@github.com wrote:
|
This in part addresses pandas-dev#3340. I added a few comments in the doc that point users ad using the pandas at, iat, loc, iloc, etc. methods and included an example similar to the one exposed in pandas-dev#3340 that addresses some of the reference / value intricaies encountered with pandas and numpy objects. CLN: cleanup + edits - addresses recent discussion CLN: cleanup II CLN: wrap at 80 chars. took care of both documents.
Wrapped, rebased. |
DOC: ref / val caveat, point at pandas methods - thanks!
@dengemann I moved the view vs copy example to consolidate with the section we had for it; I think should actually expand this example to show a proper assignment using .loc/.iloc (using your example), want to do this? |
Thanks!
Sure, I might find some time tonight. |
This in part addresses #3340.
I added a few comments in the doc that point users ad using the pandas
at, iat, loc, iloc, etc. methods and included an example similar to
the one exposed in #3340 that addresses some of the reference / value
intricaies encountered with pandas and numpy objects.
To make things clear I selected a rather verbose style.
Let me know if this is over the top ;-)