Mailman 3 August 2019 - docs

[issue37867] docs says subprocess.run accepts a string but this does not work on linux
by SilentGhost 15 Aug '19

15 Aug '19

SilentGhost <ghost.adh(a)runbox.com> added the comment: But docs don't say that at all. You're looking at description of an attribute of returned object. And of course it can be a string, under certain conditions. The attributes of CompletedProcess and function arguments are described in the standard way, and I haven't heard of anyone mixing the two before. ---------- resolution: -> not a bug stage: -> resolved status: open -> closed _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue37867> _______________________________________

2 1

[issue37867] docs says subprocess.run accepts a string but this does not work on linux
by SilentGhost 15 Aug '19

15 Aug '19

SilentGhost <ghost.adh(a)runbox.com> added the comment: The only place this phrase appears is in CompletedProcess.args description and it is correct there. Whether args arguments of subprocess.run (or generally Popen) can be a list or a string is discussed in Frequently Used Arguments section, and it is perfectly clear from reading the text under which condition you can pass a string as args argument. I don't think anything needs fixing, both implementation and docs are correct. ---------- assignee: -> docs@python components: +Documentation nosy: +SilentGhost, docs@python type: -> behavior _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue37867> _______________________________________

2 1

[issue37814] typing module: empty tuple syntax is undocumented
by Josh Holland 13 Aug '19

13 Aug '19

New submission from Josh Holland <anowlcalledjosh(a)gmail.com>: The empty tuple syntax in type annotations, `Tuple[()]`, is not obvious from the examples given in the documentation (I naively expected `Tuple[]` to work); it has been documented in PEP 484[1] and in mypy[2], but not in the documentation for the typing module. [1]: https://www.python.org/dev/peps/pep-0484/#the-typing-module [2]: https://github.com/python/mypy/pull/4313 ---------- assignee: docs@python components: Documentation messages: 349366 nosy: anowlcalledjosh, docs@python priority: normal severity: normal status: open title: typing module: empty tuple syntax is undocumented type: enhancement _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue37814> _______________________________________

5 12

[issue37813] PEP 7 line-breaking with binary operations contradicts Knuth's rule
by Géry 13 Aug '19

13 Aug '19

New submission from Géry <gery.ogam(a)gmail.com>: I have just read PEP 7 and noticed that its line-breaking recommandation in presence of binary operations seems to contradict its analogue in PEP 8 which follows Knuth's rule. PEP 7 (https://www.python.org/dev/peps/pep-0007/#code-lay-out): > When you break a long expression at a binary operator, the operator > goes at the end of the previous line, and braces should be formatted > as shown. E.g.: > > if (type->tp_dictoffset != 0 && base->tp_dictoffset == 0 && > type->tp_dictoffset == b_size && > (size_t)t_size == b_size + sizeof(PyObject *)) > { > return 0; /* "Forgive" adding a __dict__ only */ > } PEP 8 (https://www.python.org/dev/peps/pep-0008/#should-a-line-break-before-or-aft…): > To solve this readability problem, mathematicians and their > publishers follow the opposite convention. Donald Knuth explains the > traditional rule in his Computers and Typesetting series: "Although > formulas within a paragraph always break after binary operations and > relations, displayed formulas always break before binary operations" > [3]. > > Following the tradition from mathematics usually results in more > readable code: > > # Yes: easy to match operators with operands > income = (gross_wages > + taxable_interest > + (dividends - qualified_dividends) > - ira_deduction > - student_loan_interest) > In Python code, it is permissible to break before or after a binary > operator, as long as the convention is consistent locally. For new > code Knuth's style is suggested. ---------- assignee: docs@python components: Documentation messages: 349361 nosy: docs@python, maggyero priority: normal severity: normal status: open title: PEP 7 line-breaking with binary operations contradicts Knuth's rule type: enhancement versions: Python 3.7 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue37813> _______________________________________

5 5

[issue8243] curses writing to window's bottom right position raises: `_curses.error: addstr() returned ERR'
by Anthony Sottile 13 Aug '19

13 Aug '19

Anthony Sottile <asottile(a)umich.edu> added the comment: In case it helps someone else, `insstr` seems to not have this limitation ---------- nosy: +Anthony Sottile _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue8243> _______________________________________

1 0

File included in bdist
by fin swimmer 12 Aug '19

12 Aug '19

Hello, for sdist there is a documentation which files are included by default into the distribution: https://docs.python.org/3/distutils/sourcedist.html#specifying-the-files-to… I cannot found this for bdist. So which files are included by default? Thanks a lot for an answer. Fin Swimmer

1 0

[issue23220] IDLE: Document how Shell displays user code output
by Tal Einat 12 Aug '19

12 Aug '19

Change by Tal Einat <taleinat(a)gmail.com>: ---------- pull_requests: -14939 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue23220> _______________________________________

1 0

[issue23220] IDLE: Document how Shell displays user code output
by Tal Einat 11 Aug '19

11 Aug '19

Tal Einat <taleinat(a)gmail.com> added the comment: Ah, sorry for missing that, Terry. See new issue, #37827, for the proposed change. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue23220> _______________________________________

1 0

[issue23220] IDLE: Document how Shell displays user code output
by Terry J. Reedy 11 Aug '19

11 Aug '19

Terry J. Reedy <tjreedy(a)udel.edu> added the comment: The conclusion of this discussion was that we should insert control chars, in particular \b and \r, as are into tk.Text and document the (variable) result. Please describe your proposed new behavior, how it differs from the current behavior, and why you think it better. I think that this should be a new issue. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue23220> _______________________________________

1 0

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

11 Aug '19

Terry J. Reedy <tjreedy(a)udel.edu> added the comment: IDLE's Shell has treated SyntaxWarnings as errors since 2001. I don't know if any other IDE's do the same. Raymond's example did not concern me, as I think not calling known non-callables is preferable. But not executing literal-with-is code, such as "a = 1; a is 1" and "0 is ''" is wrong. See msg349431 of #34857 for more discussion of these cases. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue15248> _______________________________________

1 0