Mailman 3 March 2017 - docs

[issue29898] PYTHONLEGACYWINDOWSIOENCODING isn't implemented
by Steve Dower March 25, 2017

March 25, 2017

Steve Dower added the comment: Sure, but you're proposing a change to a correctly documented (apart from the variable name) and released behavior. It can't be changed in 3.6, and I don't see a compelling reason to have different behavior in 3.7. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue29898> _______________________________________

1 0

[issue29898] PYTHONLEGACYWINDOWSIOENCODING isn't implemented
by Eryk Sun March 25, 2017

March 25, 2017

Eryk Sun added the comment: I prefer the name PYTHONLEGACYWINDOWSIOENCODING for symmetry with both PYTHONIOENCODING and PYTHONLEGACYWINDOWSFSENCODING, but I suppose you changed it to make it more visually distinguished from the latter. I discovered this issue due to the modified behavior of PYTHONIOENCODING. It's not really a disruptive change, but it looks wrong based solely on the --help text description of PYTHONIOENCODING. An alternative would be to set Py_LegacyWindowsStdioFlag in _Py_InitializeEx_Private either when PYTHONLEGACYWINDOWSSTDIO is set or when PYTHONIOENCODING isn't a case-insensitive match for "utf-8" with an optional :errors spec. That way people get exactly what they asked for, even if it's mojibake nonsense given the console's current input and output codepages. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue29898> _______________________________________

1 0

[issue29557] binhex documentation claims unknown bug
by David Wilemski March 25, 2017

March 25, 2017

New submission from David Wilemski: The binhex documentation has a line in it that says "As of this writing, hexbin() appears to not work in all cases." This is a bit ambiguous and there is no context for what the bug may be. It appears this line is from the first commit to the hexbin function's documentation in 1995 (https://hg.python.org/cpython/rev/3911d4a89ab0#l4.40) but the commit also has no information about what this bug may be. I also see no current open bugs for the binhex module that seem related. In 2009, there was a patch for the hexbin function but I have no idea if this is the bug from the original documentation or if it was something else entirely: https://bugs.python.org/issue6369 Given this, I believe the line should be removed unless more details about the referenced buggy behavior can be found. ---------- assignee: docs@python components: Documentation messages: 287781 nosy: David Wilemski, docs@python priority: normal pull_requests: 59 severity: normal status: open title: binhex documentation claims unknown bug versions: Python 3.7 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue29557> _______________________________________

7 14

[issue29896] ElementTree.fromstring raises undocumented UnicodeError
by R. David Murray March 25, 2017

March 25, 2017

R. David Murray added the comment: Agreed with Terry. The general policy in Python is that we let errors bubble up unless there is a good reason to do something else with them. And errors that bubble up are not, in general, documented. (In short, Python is not Java :) ---------- nosy: +r.david.murray resolution: -> not a bug stage: -> resolved status: pending -> closed _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue29896> _______________________________________

1 0

[issue29892] change statement for open() is splited into two part in middle of sentence.
by OSAMU NAKAMURA March 25, 2017

March 25, 2017

New submission from OSAMU NAKAMURA: In https://docs.python.org/3.6/library/functions.html#open , Following sentence is wrongly separated by extra asterisk. ``` FileExistsError is now raised if the file opened in exclusive creation mode ('x') already exists. ``` This mistake is introduced by https://github.com/python/cpython/commit/3929499914d47365ae744df312e16da895… ---------- assignee: docs@python components: Documentation messages: 290070 nosy: OSAMU.NAKAMURA, docs@python priority: normal severity: normal status: open title: change statement for open() is splited into two part in middle of sentence. versions: Python 3.6 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue29892> _______________________________________

3 8

[issue29474] Grammatical errors in weakref.WeakValueDictionary docs
by Mariatta Wijaya March 25, 2017

March 25, 2017

New submission from Mariatta Wijaya: https://docs.python.org/3/library/weakref.html?highlight=weakref#weakref.We… There are grammatical errors in the sentence: These method have the same issues as the and keyrefs() method of WeakKeyDictionary objects. Reported by Arthur Goldberg in https://mail.python.org/pipermail/docs/2017-February/029957.html ---------- assignee: docs@python components: Documentation keywords: easy messages: 287241 nosy: Mariatta, docs@python priority: normal severity: normal status: open title: Grammatical errors in weakref.WeakValueDictionary docs versions: Python 3.5, Python 3.6, Python 3.7 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue29474> _______________________________________

4 17

[issue28911] Clarify the behaviour of assert_called_once_with
by Arne de Laat March 25, 2017

March 25, 2017

New submission from Arne de Laat: The name assert_called_once_with and the current method documentation can be interpreted to mean that it asserts that there is precisely one call matching the given signature, regardless of the total number of calls. However, the method first checks that there is precisely one call, and then checks if that call has a signature matching the provided signature. Additionally, the assert_any_call method documentation references assert_called_once_with in a way that enforces the possible misinterpretation: "… assert_called_with and assert_called_once_with that only pass if the call is the most recent one". This may lead to the interpretation that there must be only one call with the given signature and that it must be the most recent one, it must in fact be the only one. In the mock examples documentation there is an important sentence that clarifies the actual functionality: "you can use the assert_called_once_with method that also asserts that the call_count is one". The example provided in the method documentation also does not satisfactorily address the ambiguity, because it only calls the mock with one call signature. By changing the call signature of the second call (and in the assert) in the example the purpose of the method becomes clearer. ---------- assignee: docs@python components: Documentation, Tests files: assert_once_with_doc.patch keywords: patch messages: 282740 nosy: 153957, docs@python priority: normal severity: normal status: open title: Clarify the behaviour of assert_called_once_with type: enhancement versions: Python 3.3, Python 3.4, Python 3.5, Python 3.6, Python 3.7 Added file: http://bugs.python.org/file45803/assert_once_with_doc.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue28911> _______________________________________

5 14

[issue28814] Deprecation notice on inspect.getargvalues() is incorrect
by Nick Coghlan March 25, 2017

March 25, 2017

New submission from Nick Coghlan: inspect.getargvalues() and inspect.formatargvalues() were deprecated in Python 3.5 as part of implementing issue 20438 This is incorrect, as these are *frame* introspection related functions, not callable introspection ones. The documentation and implementation layout is confusing though, as they're interleaved with the callable introspection operations. ---------- assignee: docs@python components: Documentation messages: 281824 nosy: docs@python, ncoghlan, yselivanov priority: normal severity: normal stage: needs patch status: open title: Deprecation notice on inspect.getargvalues() is incorrect type: enhancement versions: Python 3.5, Python 3.6, Python 3.7 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue28814> _______________________________________

3 10

[issue29648] Missed reference to create_module() in versionadded (import.rst)
by Mariatta Wijaya March 25, 2017

March 25, 2017

Mariatta Wijaya added the comment: New changeset 46ce7599af82a929506baeaaee5c149970440c4c by Mariatta (Marco Buttu) in branch 'master': bpo-29648: import.rst: Add reference to create_module() (GH-290) https://github.com/python/cpython/commit/46ce7599af82a929506baeaaee5c149970… ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue29648> _______________________________________

1 0

[issue22594] Add a link to the regex module in re documentation
by Serhiy Storchaka March 25, 2017

March 25, 2017

New submission from Serhiy Storchaka: The regex module is purposed as a replacement of standard re module. Of course we fix re bugs, but for now regex is more bugfree. Even after fixing all open re bugs, regex will remain more featured. It would be good to add a link to regex in re documentation (as there are links to other GUI libraries in Tkinter documentation). ---------- assignee: docs@python components: Documentation, Regular Expressions keywords: easy messages: 228961 nosy: docs@python, ezio.melotti, mrabarnett, pitrou, serhiy.storchaka priority: normal severity: normal status: open title: Add a link to the regex module in re documentation type: enhancement versions: Python 2.7, Python 3.4, Python 3.5 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue22594> _______________________________________

11 26