Mailman 3 August 2021 - Docs-bugs

[issue32835] Add documention mentioning that Cygwin isn't fully compatible
by Diana 31 Aug '21

31 Aug '21

Diana <zemlya3018(a)gmail.com> added the comment: Hi, I've created a pull request for pep 11. https://github.com/python/peps/pull/2065 ---------- nosy: +DonnaDia _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue32835> _______________________________________

1 0

[issue17576] PyNumber_Index() is not int-subclass friendly (or operator.index() docs lie)
by Serhiy Storchaka 31 Aug '21

31 Aug '21

Serhiy Storchaka <storchaka+cpython(a)gmail.com> added the comment: PyNumber_Index() now always returns an instance of int. - If the argument is a direct int then return it. - If it is a subclass of int then return a direct int copy. - Otherwise call type(obj).__index__(obj) - If a direct int, return it - If a subclass of int, raise a DeprecationWarning and return a direct int copy - If not an int, raise TypeError If we go in this direction we should add a DeprecationWarning for __str__() returning not direct str. I am not sure that it is right. It adds a burden on authors of special methods to always convert the result to the corresponding direct type, while this conversion can silently (and more efficiently) be performed in the interpreter core. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue17576> _______________________________________

1 0

[issue44925] [docs] Confusing deprecation notice for typing.IO
by Łukasz Langa 31 Aug '21

31 Aug '21

Łukasz Langa <lukasz(a)langa.pl> added the comment: Thanks for the report, Jesse, and Diana for the fix! ✨ 🍰 ✨ ---------- nosy: +lukasz.langa resolution: -> fixed stage: patch review -> resolved status: open -> closed _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue44925> _______________________________________

1 0

[issue44925] [docs] Confusing deprecation notice for typing.IO
by miss-islington 31 Aug '21

31 Aug '21

miss-islington <mariatta.wijaya+miss-islington(a)gmail.com> added the comment: New changeset 1d0c5596142eeb35fea172c3642e23aeca128f5d by Miss Islington (bot) in branch '3.10': bpo-44925: [docs] Fix confusing deprecation notice for typing.IO (GH-28004) https://github.com/python/cpython/commit/1d0c5596142eeb35fea172c3642e23aeca… ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue44925> _______________________________________

1 0

[issue44925] [docs] Confusing deprecation notice for typing.IO
by Ken Jin 31 Aug '21

31 Aug '21

Ken Jin <kenjin4096(a)gmail.com> added the comment: New changeset edae42f99f8153b92ccf365dbd1c2fa954f913b4 by DonnaDia in branch 'main': bpo-44925: [docs] Fix confusing deprecation notice for typing.IO (GH-28004) https://github.com/python/cpython/commit/edae42f99f8153b92ccf365dbd1c2fa954… ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue44925> _______________________________________

1 0

[issue44925] [docs] Confusing deprecation notice for typing.IO
by miss-islington 31 Aug '21

31 Aug '21

Change by miss-islington <mariatta.wijaya+miss-islington(a)gmail.com>: ---------- nosy: +miss-islington nosy_count: 7.0 -> 8.0 pull_requests: +26527 pull_request: https://github.com/python/cpython/pull/28084 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue44925> _______________________________________

1 0

[issue44983] Wrong definition of a starred expression in the Language Reference
by Takuo Matsuoka 30 Aug '21

30 Aug '21

New submission from Takuo Matsuoka <motogeomtop(a)gmail.com>: Being unaware of the processes here, I have posted the issue to the python-idea mailing list. Please refer to it. https://mail.python.org/archives/list/python-ideas@python.org/message/TCWYZ… Thank you. ---------- assignee: docs@python components: Documentation messages: 400136 nosy: Takuo Matsuoka, docs@python priority: normal severity: normal status: open title: Wrong definition of a starred expression in the Language Reference type: behavior versions: Python 3.9 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue44983> _______________________________________

2 3

[issue17576] PyNumber_Index() is not int-subclass friendly (or operator.index() docs lie)
by Raymond Hettinger 30 Aug '21

30 Aug '21

Raymond Hettinger <raymond.hettinger(a)gmail.com> added the comment: > So I really *do* want to see the ability of __float__ > to return a non-float eventually removed. Note, the __str__ method on strings does not require an exact str. class S: def __str__(self): return self print(type(str(S('hello world')))) ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue17576> _______________________________________

1 0

[issue44756] In ./Doc, "make html" and "make build" should depend on "make venv"
by Jack DeVries 30 Aug '21

30 Aug '21

New submission from Jack DeVries <jdevries3133(a)gmail.com>: In Doc/Makefile, all of the build rules should be dependent on the existence of a virtual environment. I could see this being controversial, because folks who have these tools installed elsewhere might prefer not to have a venv made for them, but my personal workflow is to strive to keep my system site-packages folder as empty as possible and to use virtual environments frequently. In any case, I'm interested to hear what we think. Momentarily, I will attach a PR where I went ahead and made these changes. Here is a summary of the changes: - venv rule is now conditional, and only does anything if $VENVDIR does not exist - add rule "clean-venv". This can be removed – what do you all think? - build rule is dependent on venv - as a result, rules dependent on build are dependent on venv - html - latex - etc. - update Doc/README.rst appropriately. Now users only need to type ``make html`` – nice! Let me know what you think. I may have a blind spot to others' workflows! Also, I'm not a Windows user, so I have no insight as to whether ``make.bat`` needs to be updated as well. ---------- assignee: docs@python components: Demos and Tools, Documentation messages: 398344 nosy: docs@python, jack__d priority: normal severity: normal status: open title: In ./Doc, "make html" and "make build" should depend on "make venv" type: enhancement versions: Python 3.11 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue44756> _______________________________________

7 26

[issue39452] Improve the __main__ module documentation
by Guido van Rossum 30 Aug '21

30 Aug '21

Guido van Rossum <guido(a)python.org> added the comment: Thanks, the rewrite is great! I have one nit: did you consider which of these two idioms is better? if __name__ == "__main__": main() vs. if __name__ == "__main__": sys.exit(main()) Your docs seem to promote the second, whereas I've usually preferred the former. Was this a considered choice on your part? ---------- nosy: +gvanrossum _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue39452> _______________________________________

1 0