[issue13203] Doc: say id() is only useful for existing objects

2013-10-12 Thread Roundup Robot
Roundup Robot added the comment: New changeset 0d5de993db66 by Georg Brandl in branch '3.3': Closes #13203: add a FAQ section about seemingly duplicate id()s. http://hg.python.org/cpython/rev/0d5de993db66 -- ___ Python tracker

[issue13203] Doc: say id() is only useful for existing objects

2013-10-12 Thread Roundup Robot
Roundup Robot added the comment: New changeset 8525cc1f342f by Georg Brandl in branch '2.7': Closes #13203: add a FAQ section about seemingly duplicate id()s. http://hg.python.org/cpython/rev/8525cc1f342f -- nosy: +python-dev resolution: -> fixed stage: needs patch -> committed/rejected

[issue13203] Doc: say id() is only useful for existing objects

2013-10-12 Thread Ezio Melotti
Ezio Melotti added the comment: LGTM + created and deleted during execution of the ``id()`` If you want to be more accurate you could say "before and after" instead of "during". -- ___ Python tracker ___

[issue13203] Doc: say id() is only useful for existing objects

2013-10-12 Thread Georg Brandl
Georg Brandl added the comment: Suggestion attached. -- keywords: +patch Added file: http://bugs.python.org/file32059/id_unique.diff ___ Python tracker ___ __

[issue13203] Doc: say id() is only useful for existing objects

2011-10-21 Thread Ezio Melotti
Ezio Melotti added the comment: A FAQ entry sounds good to me. -- nosy: +ezio.melotti stage: -> needs patch ___ Python tracker ___ _

[issue13203] Doc: say id() is only useful for existing objects

2011-10-21 Thread Éric Araujo
Changes by Éric Araujo : -- nosy: +eric.araujo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue13203] Doc: say id() is only useful for existing objects

2011-10-17 Thread Raymond Hettinger
Changes by Raymond Hettinger : -- assignee: docs@python -> rhettinger ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

[issue13203] Doc: say id() is only useful for existing objects

2011-10-17 Thread Raymond Hettinger
Raymond Hettinger added the comment: I think this is over-explaining an implementation detail and it makes the docs for id() harder to understand. Possibly there can be a FAQ entry about identity but the id() function itself is no place to go into the quirks of when new objects are created or

[issue13203] Doc: say id() is only useful for existing objects

2011-10-17 Thread Terry J. Reedy
Terry J. Reedy added the comment: I gave a maximum addition. The first sentence may be enough (or even just the second half of it). What people do not get is that the lifetime of new arg objects is the duration of the function call -- and that the output of id for departed objects is uniquely

[issue13203] Doc: say id() is only useful for existing objects

2011-10-17 Thread Georg Brandl
Georg Brandl added the comment: If we add something at all, it should be much shorter. After all, the current doc already states "unique during its lifetime". -- nosy: +georg.brandl, rhettinger priority: normal -> low ___ Python tracker

[issue13203] Doc: say id() is only useful for existing objects

2011-10-17 Thread Terry J. Reedy
New submission from Terry J. Reedy : Newbies too often do something like (3.2.2, ) >>> id(getattr(x, 'pop')) == id(x.pop) True and get confused by the (invalid) result, whereas >>> a,b=getattr(x, 'pop'),x.pop >>> id(a)==id(b) False works properly. I think we should add a sentence or two or th