[issue27825] Make the documentation for statistics' data argument clearer.

Roundup Robot added the comment: New changeset 71dd21a3b9cc by Raymond Hettinger in branch '3.6': Issue #27825: Improve for statistics data arguments. (Contributed by Mariatta Wijaya.) https://hg.python.org/cpython/rev/71dd21a3b9cc -- nosy: +python-dev _

[issue28587] list.index documentation missing start and stop arguments

Roundup Robot added the comment: New changeset efac7ac53933 by Raymond Hettinger in branch '3.6': Issue #28587: Improve list examples in the tutorial https://hg.python.org/cpython/rev/efac7ac53933 -- ___ Python tracker

[issue27825] Make the documentation for statistics' data argument clearer.

Raymond Hettinger added the comment: Thanks Mariatta. As discussed in chat, I dropped the extra fractions examples because they didn't seem to add value. -- nosy: +rhettinger resolution: -> fixed status: open -> closed ___ Python tracker

[issue27825] Make the documentation for statistics' data argument clearer.

Mariatta Wijaya added the comment: Sounds good. Thanks, Raymond :) -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

[issue28587] list.index documentation missing start and stop arguments

Raymond Hettinger added the comment: Okay, applied. -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue5830] heapq item comparison problematic with sched's events

Roundup Robot added the comment: New changeset ecc6f7940e02 by Raymond Hettinger in branch '3.6': Issue #5830: Add test for ee476248a74a. (Contributed by Serhiy Storchaka.) https://hg.python.org/cpython/rev/ecc6f7940e02 -- ___ Python tracker

[issue5830] heapq item comparison problematic with sched's events

Raymond Hettinger added the comment: Thanks Serhiy. FWIW, I changed the variable name from "l" to "seq" for readability. -- status: open -> closed ___ Python tracker ___

[issue28763] Use en-dashes for ranges in docs

Martin Panter added the comment: Personally I prefer en dashes where practical, but I fear the change may conflict with other people’s styles and preferences. I quickly counted 22 single hyphens (obviously I missed a few that your patch caught) and also 22 existing en dashes. --

[issue26163] FAIL: test_hash_effectiveness (test.test_set.TestFrozenSet)

Raymond Hettinger added the comment: Rather than making futile further attempts to scramble the bits in the final hash to hide the effect of weak upstream hash inputs, I'm inclined to disable this particular test which was already a crazily harsh torture test. I suspect that even the tuple ha

[issue26163] FAIL: test_hash_effectiveness (test.test_set.TestFrozenSet)

Roundup Robot added the comment: New changeset e0f0211d314d by Raymond Hettinger in branch '3.6': Issue #26163: Disable periodically failing test which was overly demanding of the frozenset hash function effectiveness https://hg.python.org/cpython/rev/e0f0211d314d -- nosy: +python-dev

[issue26163] FAIL: test_hash_effectiveness (test.test_set.TestFrozenSet)

Changes by Raymond Hettinger : -- resolution: -> wont fix status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing

[issue28688] Warning -- warnings.filters was modified by test_warnings

Martin Panter added the comment: As long as we are restricted by backwards compatibility, it will be hard to find a hack-free solution. The ideal solution IMO is to re-create _warnings.filters from scratch when _warnings is reloaded, but such a change would be safer only for 3.7. So I am happ

[issue28688] Warning -- warnings.filters was modified by test_warnings

Changes by Martin Panter : -- superseder: Warning -- warnings.filters was modified by test_warnings -> Implement comparison (x==y and x!=y) for _sre.SRE_Pattern ___ Python tracker _

[issue28766] Remove the semicolon in source code

Martin Panter added the comment: This was added to 2.7 in r68532 (Issue 4879), but the semicolon never made it to the Python 3 branch that I can see, so I don’t think there is anything to fix there. Your patch is against the 2.7 branch, which is only open for bug fixes now, and I don’t think t

[issue27100] Attempting to use class with both __enter__ & __exit__ undefined yields __exit__ attribute error

Roundup Robot added the comment: New changeset 3aafb232f2db by Raymond Hettinger in branch '3.6': Issue #27100: With statement reports missing __enter__ before __exit__. (Contributed by Jonathan Ellington.) https://hg.python.org/cpython/rev/3aafb232f2db -- nosy: +python-dev _

[issue27100] Attempting to use class with both __enter__ & __exit__ undefined yields __exit__ attribute error

Raymond Hettinger added the comment: Thanks for the patch Jonathan. Nick, thanks for chiming in. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ _

[issue23106] Remove smalltable from set objects

Raymond Hettinger added the comment: Based on the performance hit, I am retracting this. -- resolution: -> rejected status: open -> closed ___ Python tracker ___ ___

[issue28738] Document SIGBREAK as argument for signal() under Windows.

Changes by Eryk Sun : -- keywords: +easy priority: normal -> low stage: -> patch review versions: +Python 3.6 ___ Python tracker ___

[issue28702] Confusing error message when None used in expressions, eg. "'NoneType' object has no attribute 'foo'"

Greg Ward added the comment: > Is it worth changing about 800 places in CPython code? Not counting > third-party code. Definitely not. My aim is not to fix every possible reference to "instance of 'NoneType'", just the handful of cases that are most frequently encountered, especially if we th

[issue28763] Use en-dashes for ranges in docs

Serhiy Storchaka added the comment: The rest single hyphens between digits are meaningful hypens in iso-8859-1, ISDNs, sample outputs, etc. -- ___ Python tracker ___ ___

[issue28763] Use en-dashes for ranges in docs

Martin Panter added the comment: Sure, I was just saying that for whatever reason, 50% of the documentation uses hyphens for number ranges, and 50% uses en dashes. -- ___ Python tracker ___

[issue28635] Update What's New for 3.6

INADA Naoki added the comment: I added ``-VV`` option to python command (issue28532). Which section should I add the entry about it? -- nosy: +inada.naoki ___ Python tracker ___

[issue28766] Remove the semicolon in source code

Yuwei Ba added the comment: I know this is not a functional 'fix', though it's the fact that there should not be a semicolon. It can make user confusing. There might be another user who found this semicolon and create an issue again since there are still lots of Python27 codes running on tons

[issue28761] Add the const qualifier to fields name and doc of public structs

Roundup Robot added the comment: New changeset 42b0ba372ec2 by Serhiy Storchaka in branch 'default': Issue #28761: The fields name and doc of structures PyMemberDef, PyGetSetDef, https://hg.python.org/cpython/rev/42b0ba372ec2 -- nosy: +python-dev ___

[issue5830] heapq item comparison problematic with sched's events

Serhiy Storchaka added the comment: Agreed, "seq" is better name. Thanks Raymond. -- ___ Python tracker ___ ___ Python-bugs-list maili

[issue5830] heapq item comparison problematic with sched's events

Changes by Serhiy Storchaka : -- stage: -> resolved ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue28761] Add the const qualifier to fields name and doc of public structs

Serhiy Storchaka added the comment: Thanks Nick. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue28761] Add the const qualifier to fields name and doc of public structs

Changes by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ _

[issue28573] Python 3.6.0b4 64-bit has no sys._mercurial info

Steve Dower added the comment: Wasn't fixed as well as I'd like, so I clearly need a better approach here. -- resolution: fixed -> stage: resolved -> status: closed -> open title: Python 3.6.0b3 64-bit has no sys._mercurial info -> Python 3.6.0b4 64-bit has no sys._mercurial info ___

[issue28766] Remove the semicolon in source code

Raymond Hettinger added the comment: Sorry Yuwei, but this is irrelevant and not appropriate for a Python 2.7 backport at this time. -- nosy: +rhettinger status: open -> closed ___ Python tracker _

[issue28769] Make PyUnicode_AsUTF8 returning "const char *" rather of "char *"

New submission from Serhiy Storchaka: PyUnicode_AsUTF8AndSize() and PyUnicode_AsUTF8() return a reference to cached readonly UTF-8 representation of a string. Changing the content of the UTF-8 representation is an error. Proposed patch makes these functions returning "const char *" rather of "

<    1   2