Mailman 3 December 2020 - docs

Python GUI library - Dear PyGui
by Wiebe van der Waals 23 Dec '20

23 Dec '20

Dear reader, I'd like to suggest that the Dear PyGui be added to the Python GUI's listed on https://docs.python.org/3/faq/gui.html Below you will find a a paragraph of text that could be included on that page. *Dear PyGui* <https://docs.python.org/3/faq/gui.html> is an easy-to-use, flexible, powerful cross-platform GUI framework for Python (Windows, Linux and MacOS). As an extended wrapping of Dear ImGui, Dear PyGui is highly performant. It is written primarily in C/C++ and uses your GPU for rendering. Features include traditional GUI elements to display text, images and various controls, such as buttons, radio buttons, and menus and various methods to create a functional and beautiful layout. Additionally, it offers incredibly dynamic charts, tables, drawings and tools for application development, such as built-in documentation, logging, and a debugger. As a GUI toolkit, it is well suited for creating simple user interfaces to wrap basic command line interfaces as well as to developing complex and demanding graphical interfaces. It offers a solid framework for developing science, engineering, games, data science and other applications that require fast and interactive interfaces. Dear PyGui Github: https://github.com/hoffstadt/DearPyGui/ Dear PyGui Homepage: https://hoffstadt.github.io/DearPyGui/ Thank you for your consideration! Kind regards, Wiebe van der Waals

1 0

[issue9694] argparse required arguments displayed under "optional arguments"
by Raymond Hettinger 23 Dec '20

23 Dec '20

Change by Raymond Hettinger <raymond.hettinger(a)gmail.com>: ---------- resolution: -> fixed stage: patch review -> resolved status: open -> closed _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue9694> _______________________________________

1 0

[issue9694] argparse required arguments displayed under "optional arguments"
by Raymond Hettinger 23 Dec '20

23 Dec '20

Raymond Hettinger <raymond.hettinger(a)gmail.com> added the comment: New changeset 41b223d29cdfeb1f222c12c3abaccc3bc128f5e7 by Raymond Hettinger in branch 'master': bpo-9694: Fix misleading phrase "optional arguments" (GH-23858) https://github.com/python/cpython/commit/41b223d29cdfeb1f222c12c3abaccc3bc1… ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue9694> _______________________________________

1 0

Bug in python core!!!
by hooman ghamari 23 Dec '20

23 Dec '20

Dear Sirs and Mesdames, I found an interesting bug on Python 3.8 programming language core, The answer of some calculations like 9.7-0.3 will be shown 9.399999999999999 !!!! Please take a look at the picture. Sincerely yours,Hooman Ghamari

2 1

[Turtle] Missing documentation about undobuffer
by epersonnal＠keemail.me 23 Dec '20

23 Dec '20

Hello, the documentation about undobuffer isn't clear. Especially setundobuffer Logically, once you call setundobuffer(None), it should stay that way. But setundobuffer() does not set _undobuffersize. Which means that clear() resets the undobuffer back to its original size. This may be the intended behaviour, but it should be written in the documentation.

1 0

[issue42703] Asyncio Event Documentation Links Incorrect
by Matt Fowler 23 Dec '20

23 Dec '20

New submission from Matt Fowler <matt.fow(a)gmail.com>: The documentation for `asyncio.Event` has incorrect links. The `wait` coroutine incorrectly links to the docs for the `asyncio.wait` waiting primitive, and the `set` method incorrectly links to the docs for the `set` class constructor. ---------- assignee: docs@python components: Documentation messages: 383524 nosy: docs@python, mattfowler priority: normal severity: normal status: open title: Asyncio Event Documentation Links Incorrect versions: Python 3.10, Python 3.9 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue42703> _______________________________________

3 7

[issue9694] argparse required arguments displayed under "optional arguments"
by Eric V. Smith 22 Dec '20

22 Dec '20

Eric V. Smith <eric(a)trueblade.com> added the comment: I wouldn't let breaking these tests deter you from improving the output. I think using "options" is an improvement. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue9694> _______________________________________

1 0

[issue9694] argparse required arguments displayed under "optional arguments"
by Raymond Hettinger 22 Dec '20

22 Dec '20

Raymond Hettinger <raymond.hettinger(a)gmail.com> added the comment: Since this change will break tests that rely matching help output exactly, I would like to hear if there are any objections to replacing "optional arguments" with "options". The words "switch" or "flag" don't work as well because they imply on/off and don't encompass option that take arguments. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue9694> _______________________________________

1 0

[issue35783] incorrect example of fetching messages in imaplib documentation
by Макс Вернер 22 Dec '20

22 Dec '20

New submission from Макс Вернер <mvarnar(a)gmail.com>: An example of fetching messages from the mailbox given in "IMAP4 Example" section is incorrect: typ, data = M.fetch(num, '(RFC822)') print('Message %s\n%s\n' % (num, data[0][1])) "fetch" may return server data that was not requested (see "7.4.2. FETCH Response" section of RFC 3501). In that case "data[0][1]" won't return what user expects. This is a bad example, that many people repeat and advise to other developers: https://stackoverflow.com/questions/13210737/get-only-new-emails-imaplib-an… https://gist.github.com/robulouski/7441883 https://stackoverflow.com/questions/51098962/check-if-email-inbox-is-empty-… https://stackoverflow.com/questions/21116498/imaplib-not-getting-all-emails… https://stackoverflow.com/questions/2230037/how-to-fetch-an-email-body-usin… I guess, this peculiarity should be clarified in the documentation. I offer to mark this fetching method is not safe and requests careful fetch result parsing. ---------- assignee: docs@python components: Documentation, email messages: 334048 nosy: barry, docs@python, r.david.murray, Макс Вернер priority: normal severity: normal status: open title: incorrect example of fetching messages in imaplib documentation type: enhancement versions: Python 2.7, Python 3.5, Python 3.6, Python 3.7, Python 3.8 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue35783> _______________________________________

2 1

[issue42710] Viewing pydoc API documentation
by Faris Chugthai 21 Dec '20

21 Dec '20

New submission from Faris Chugthai <farischugthai(a)gmail.com>: I'm sure that this has been observed before, but I was unable to find the original issue where this was discussed so I'm going to apologize in advance for what is probably a duplicate issue. But why is there no documentation available on the classes and functions available in the pydoc module? There are a large number of well documented classes, methods and functions and I could easily imagine legitimate motivations to want to import some of the functionality provided and use it in a project. No information on the 2000 lines of code in pydoc.py are provided at https://docs.python.org/3/library/pydoc.html Running: `python -m pydoc -w pydoc` Generates a similarly sparse file. In addition, running in the interactive interpreter: >>> help(pydoc) shows almost no real information. I'm genuinely unsure of why this happens. Even if this is an intentional design decision for how the Helper class is supposed to work, why isn't there corresponding information for the different classes at `Doc/library/pydoc.rst`? Searching for something like `pydoc.TextRepr` in the search bar of docs.python.org doesn't return anything at all. Sorry if there's something horrifically obvious I'm missing here guys but I'd appreciate any clarification on this matter. ---------- assignee: docs@python components: Documentation messages: 383570 nosy: Faris Chugthai, docs@python priority: normal severity: normal status: open title: Viewing pydoc API documentation _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue42710> _______________________________________

1 0