[issue34123] ambiguous documentation for dict.popitem

2018-07-16 Thread Raymond Hettinger
Change by Raymond Hettinger : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue34123] ambiguous documentation for dict.popitem

2018-07-16 Thread Raymond Hettinger
Raymond Hettinger added the comment: New changeset bfa8a358e2cec40484c4655138ca3c6b10f8462a by Raymond Hettinger (Miss Islington (bot)) in branch '3.7': bpo-34123: Fix missed documentation update for dict.popitem(). (GH-8292) (GH#8307) https://github.com/python/cpython/commit/bfa8a358e2cec40

[issue34123] ambiguous documentation for dict.popitem

2018-07-16 Thread Raymond Hettinger
Raymond Hettinger added the comment: New changeset 01b7d5898262dbe0e9edb321b3be9a34da196f6f by Raymond Hettinger in branch 'master': bpo-34123: Fix missed documentation update for dict.popitem(). (GH-8292) https://github.com/python/cpython/commit/01b7d5898262dbe0e9edb321b3be9a34da196f6f ---

[issue34123] ambiguous documentation for dict.popitem

2018-07-16 Thread miss-islington
Change by miss-islington : -- pull_requests: +7842 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

[issue34123] ambiguous documentation for dict.popitem

2018-07-16 Thread Armin Rigo
Armin Rigo added the comment: Agreed with Raymond. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:

[issue34123] ambiguous documentation for dict.popitem

2018-07-16 Thread Raymond Hettinger
Raymond Hettinger added the comment: > Is there no possible optimizations by breaking LIFO dict.popitem()? Even if there were a possible optimization, we wouldn't care. The API is too desirable to forgo in the name of micro-optimization. We don't design our APIs that way -- trading the rel

[issue34123] ambiguous documentation for dict.popitem

2018-07-16 Thread INADA Naoki
INADA Naoki added the comment: @Armin Rigo How do you think about this? Is there no possible optimizations by breaking LIFO dict.popitem()? -- nosy: +arigo ___ Python tracker

[issue34123] ambiguous documentation for dict.popitem

2018-07-16 Thread Raymond Hettinger
Change by Raymond Hettinger : -- keywords: +patch pull_requests: +7826 stage: -> patch review ___ Python tracker ___ ___ Python-bug

[issue34123] ambiguous documentation for dict.popitem

2018-07-15 Thread Raymond Hettinger
Change by Raymond Hettinger : -- assignee: docs@python -> rhettinger ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubs

[issue34123] ambiguous documentation for dict.popitem

2018-07-15 Thread Raymond Hettinger
Raymond Hettinger added the comment: My opinion is that it is in fact guaranteed. It makes no sense for all other aspects of the dict behavior to be guaranteed and not this one. This is what PyPy and CPython already do and there is no scenario where an implementation would be able to append

[issue34123] ambiguous documentation for dict.popitem

2018-07-15 Thread INADA Naoki
INADA Naoki added the comment: I think it is implementation detail yet. Only iteration order is guaranteed. -- nosy: +inada.naoki ___ Python tracker ___ __

[issue34123] ambiguous documentation for dict.popitem

2018-07-15 Thread Dan Snider
New submission from Dan Snider : https://docs.python.org/3/library/stdtypes.html#dict.popitem `dict.popitem` no longer returns an "arbitrary" (key, value) pair as the documentation suggests. Rather, it always returns the pair whose key was most recently *inserted* (ie., the last entry in `dk