Mailman 3 January 2017 - docs

[issue29134] contextlib doc bug
by Kyle Altendorf 04 Jan '17

04 Jan '17

Kyle Altendorf added the comment: I would think that the idea of simply adding some reference to `User` such as was suggested with `UserDefinedContextClass` would be reasonable and helpful. This doesn't involve any more code merely a more explanatory name. ---------- nosy: +altendky _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue29134> _______________________________________

1 0

Documentation error
by lima neto 04 Jan '17

04 Jan '17

I think I've found a typo in your documentation, here it follows the print, I think the error is located in the part where you say: "This method will return normally if the mail is accepted for at least one recipient. Otherwise it will raise an exception. That is, if this method does not raise an exception, then someone should get your mail. If this method does not raise an exception, it returns a dictionary, with one entry for each recipient that was refused. Each entry contains a tuple of the SMTP error code and the accompanying error message sent by the server." was it not suppose to say: "This method will return normally if the mail is accepted for at least one recipient. Otherwise it will raise an exception. That is, if this method does not raise an exception, then someone should get your mail. If this method DOES raise an exception, it returns a dictionary, with one entry for each recipient that was refused. Each entry contains a tuple of the SMTP error code and the accompanying error message sent by the server. ?

1 0

[issue29134] contextlib doc bug
by Senthil Kumaran 04 Jan '17

04 Jan '17

Senthil Kumaran added the comment: I am going to vote for "not a bug" here. From the context is it understood that the `ContextBaseClass` is to be provided by the user. > Existing context managers that already have a base class can be extended by using ContextDecorator as a mixin class: The idea here is the illustrate the Mixin possibility with a Base class and not to provide a full example with Base class code as well. @Marco, also not a good ticket add more doc strings to this module.rst. If the docs of those can be improved, they can done separately, concentrating on all the possible improvements. ---------- nosy: +orsenthil resolution: -> not a bug status: open -> closed _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue29134> _______________________________________

1 0

[issue29146] Confusing "invalid token" exception when integers have leading zero
by John Parejko 04 Jan '17

04 Jan '17

New submission from John Parejko: As described in PEP-3127, the "leading-zeros" formatting for octal was removed from python 3. This is a good thing(tm), but the recommendation of that PEP to improve the error message of the raised exception[1] was apparently never implemented. I just ran into this while with some recently-ported python2 code, and it took a while to figure out the problem. Although this is going to be less of a problem with time as people convert to pure python3, it will be very helpful during the transition period. >>> 0o007 7 >>> 007 File "<stdin>", line 1 007 ^ SyntaxError: invalid token 1: https://www.python.org/dev/peps/pep-3127/#id17 ---------- assignee: docs@python components: 2to3 (2.x to 3.x conversion tool), Documentation, Interpreter Core messages: 284591 nosy: John Parejko, docs@python priority: normal severity: normal status: open title: Confusing "invalid token" exception when integers have leading zero type: behavior versions: Python 3.5 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue29146> _______________________________________

1 1

[issue29134] contextlib doc bug
by SilentGhost 03 Jan '17

03 Jan '17

Changes by SilentGhost <ghost.adh(a)runbox.com>: ---------- assignee: -> docs@python components: +Documentation nosy: +docs@python stage: -> patch review type: -> behavior versions: +Python 3.5, Python 3.6, Python 3.7 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue29134> _______________________________________

1 0

[issue29012] __bases__ is a tuple (possibly empty or a singleton)
by Jim Fasarakis-Hilliard 03 Jan '17

03 Jan '17

New submission from Jim Fasarakis-Hilliard: The following statement is in the Language Reference for Custom classes: > __bases__ is a tuple (possibly empty or a singleton) containing the base classes AFAIK, ``object.__bases__`` is the only object for which ``__bases__`` is empty and it isn't a *custom* class. Attempts to create a class and assign __bases__ to an empty tuple is checked to enforce inheritance from ``object``. This *seems* to be something that slipped through when the docs were created for Python 3.0? I'm curious to see if this can actually be empty, if not, attached patch removes ''empty'' from the sentence. ---------- assignee: docs@python components: Documentation files: fixbasesdoc.patch keywords: patch messages: 283595 nosy: Jim Fasarakis-Hilliard, docs@python priority: normal severity: normal status: open title: __bases__ is a tuple (possibly empty or a singleton) versions: Python 3.3, Python 3.4, Python 3.5, Python 3.6, Python 3.7 Added file: http://bugs.python.org/file45962/fixbasesdoc.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue29012> _______________________________________

5 7

[issue29129] Copy/paste error in "8.13.14.1.1. Using auto"
by Michael Mrozek 02 Jan '17

02 Jan '17

New submission from Michael Mrozek: The "8.13.14.1.1 Using auto" section ( https://docs.python.org/3/library/enum.html#using-auto ) looks like it was copied from the subsequent "8.13.14.1.2 Using object" section, and a reference to "object" wasn't changed to "auto" in the first line. ---------- assignee: docs@python components: Documentation messages: 284434 nosy: docs@python, mrozekma priority: normal severity: normal status: open title: Copy/paste error in "8.13.14.1.1. Using auto" versions: Python 3.6 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue29129> _______________________________________

3 2

[issue29024] Add Kivy entry to Graphic User Interface FAQ
by Roundup Robot 02 Jan '17

02 Jan '17

New submission from Roundup Robot: New changeset d41aa32f7f3c by Berker Peksag in branch '3.5': Issue #29024: Add Kivy entry to GUI FAQ https://hg.python.org/cpython/rev/d41aa32f7f3c New changeset ee25895d9d65 by Berker Peksag in branch '3.6': Issue #29024: Merge from 3.5 https://hg.python.org/cpython/rev/ee25895d9d65 New changeset 4eb4cf6ac154 by Berker Peksag in branch 'default': Issue #29024: Merge from 3.6 https://hg.python.org/cpython/rev/4eb4cf6ac154 ---------- nosy: +python-dev _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue29024> _______________________________________

2 1

reference doc problem
by Christopher Barry 02 Jan '17

02 Jan '17

https://docs.python.org/3.5/reference/lexical_analysis.html#keywords describes 'is' as a keyword, yet https://docs.python.org/3.5/reference/datamodel.html#objects-values-and-typ… describes 'is' as an operator. Which is it? If it really is an operator (too?), shouldn't it be here: https://docs.python.org/3.5/reference/lexical_analysis.html#operators as well? -- Regards, Christopher Barry

2 1