Mailman 3 January 2019 - docs

[issue5028] tokenize.generate_tokens doesn't always return logical line
by Roundup Robot 26 Jan '19

26 Jan '19

Change by Roundup Robot <devnull(a)psf.upfronthosting.co.za>: ---------- keywords: +patch pull_requests: +11518 stage: needs patch -> patch review _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue5028> _______________________________________

1 0

https://docs.python.org/3/tutorial/errors.html#defining-clean-up-actions
by Goldberg, Arthur P 26 Jan '19

26 Jan '19

I am suggesting an improvement. The page says “As you can see, the finally clause is executed in any event”. However the example above this sentence does not illustrate what it says. It would be better to have an example that includes a raise, break, continue, or return in the try before finally. I think it would be best to include 2 of these, probably raise and return. I can create an example if you’d like. Regards Arthur Arthur Goldberg, PhD Associate Professor of Genetics and Genomic Sciences Institute for Data Science and Genomic Technology Mount Sinai School of Medicine 1255 Fifth Ave., Suite C-2 New York, NY 10029 646 526 5020 Karr Lab Arthur.Goldberg(a)mssm.edu<mailto:Arthur.Goldberg@mssm.edu>

1 0

[issue35831] Format Spec example says limited to 3.1+ but works in 2.7
by Fred L. Drake, Jr. 25 Jan '19

25 Jan '19

Fred L. Drake, Jr. <fdrake(a)gmail.com> added the comment: The 3.X docs generally don't refer to the 2.X series. What that comment is pointing out is that leaving the field identifier out (the number inside the {...} placeholder syntax) was not in the 3.0, but added in 3.1. Unfortunately, I don't have a 3.0 interpreter available to show the exception that's raised. No change is required. ---------- nosy: +fdrake stage: -> resolved status: open -> closed _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue35831> _______________________________________

1 0

[issue35831] Format Spec example says limited to 3.1+ but works in 2.7
by Mitchell L Model 25 Jan '19

25 Jan '19

Change by Mitchell L Model <mlm(a)users.sourceforge.net>: ---------- assignee: -> docs@python components: +Documentation nosy: +docs@python _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue35831> _______________________________________

1 0

Doctest directives are not rendered into html or text?
by pydoc84＠scotdoyle.com 25 Jan '19

25 Jan '19

The html and text documentation (3.6, 3.7, 3.8) for doctest directives at Library Reference -> 26.3 Doctest -> 26.3.3.6 Directives is missing the actual directives, but they are visible in the source at master/Doc/library/doctest.rst. For example, doctest.rst has: >>> print(list(range(20))) # doctest: +NORMALIZE_WHITESPACE while the web and text documentation has: >>> print(list(range(20)))

1 0

[issue15248] Better explain "TypeError: 'tuple' object is not callable"
by Guido van Rossum 24 Jan '19

24 Jan '19

Change by Guido van Rossum <guido(a)python.org>: ---------- nosy: +gvanrossum _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue15248> _______________________________________

1 0

[issue15248] Better explain "TypeError: 'tuple' object is not callable"
by Terry J. Reedy 24 Jan '19

24 Jan '19

Terry J. Reedy <tjreedy(a)udel.edu> added the comment: I am not sure what you could do at the moment. We have not yet settled whether this is a documentation or interpreter core issue. I posted "Add more SyntaxWarnings?" to pydev to get more comments on Serhiy's patch, especially for other core developers. Depending on what people think, that *might* result in someone converting the diff (with the typo corrected) into a PR. I already posted here a prototype doc entry for TypeError messages. I decided that I should take time out from IDLE to post my idea for a separate error message doc. I will include a fleshed-out TypeError entry (with code example) as an example entry. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue15248> _______________________________________

1 0

[issue15248] Better explain "TypeError: 'tuple' object is not callable"
by Mayank Singhal 24 Jan '19

24 Jan '19

Mayank Singhal <17mayanksinghal(a)gmail.com> added the comment: Hey, if nobody is working on this can I go for it? ---------- nosy: +storymode7 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue15248> _______________________________________

1 0

[issue18610] wsgiref.validate expects wsgi.input read to give exactly one arg
by Cheryl Sabella 23 Jan '19

23 Jan '19

Change by Cheryl Sabella <cheryl.sabella(a)gmail.com>: ---------- pull_requests: -11469 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue18610> _______________________________________

1 0

[issue18610] wsgiref.validate expects wsgi.input read to give exactly one arg
by Cheryl Sabella 23 Jan '19

23 Jan '19

Change by Cheryl Sabella <cheryl.sabella(a)gmail.com>: ---------- pull_requests: -11468 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue18610> _______________________________________

1 0