[issue32123] Make the API of argparse.HelpFormatter public
New submission from Bernhard10 <th...@tbi.univie.ac.at>: Since there have not been any significant change to the code of argparse.HelpFormatter in the last few years but there are still some open issues where people want to customize formatting, I would like to ask: What is required before parts of the API of argparse.HelpFormatter can be made public? Related issues: https://bugs.python.org/issue17113 RawDescriptionHelpFormatter removes blank lines https://bugs.python.org/issue12806 and https://bugs.python.org/issue22029 request a formatter that (partly) wraps lines but keeps newlines. https://bugs.python.org/issue11695 costumize usage https://bugs.python.org/issue28742 Improve ArgumentDefaultsHelpFormatter All this issues could be fixed outside the standard library by sub-classing HelpFormatter, which would require a public and documented API for it. So my question: What is missing before HelpFormatter can get a public API and how can I help? -- components: Library (Lib) messages: 306879 nosy: Bernhard10 priority: normal severity: normal status: open title: Make the API of argparse.HelpFormatter public type: enhancement versions: Python 3.8 ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue32123> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28973] The fact that multiprocess.Queue uses serialization should be documented.
Bernhard10 added the comment: My first thought was that Queue was implemented using shared memory. I guess from the fact that the "Shared memory" section is separate in the multiprocessing documentation I should have known better, though. So I guess some clarification in the documentation would be helpful. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28973> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28973] The fact that multiprocess.Queue uses serialization should be documented.
Bernhard10 added the comment: See http://stackoverflow.com/a/925241/5069869 Apparently multiprocessing.Queue uses pickle to serialize the objects in the queue, which explains the change of identity, but is absolutely unclear from the documentation. -- assignee: -> docs@python components: +Documentation nosy: +docs@python title: multiprocess.Queue changes objects identity -> The fact that multiprocess.Queue uses serialization should be documented. ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28973> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28973] multiprocess.Queue changes objects identity
New submission from Bernhard10: When I did some tests involving unittest.mock.sentinel and multiprocessing.Queue, I noticed that multiprocessing.Queue changes the id of the sentinel. This behaviour is definitely surprising and not documented. -- files: mwe.py messages: 283192 nosy: Bernhard10 priority: normal severity: normal status: open title: multiprocess.Queue changes objects identity type: behavior versions: Python 2.7, Python 3.5 Added file: http://bugs.python.org/file45899/mwe.py ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28973> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
