Mailman 3 February 2015 - docs

[issue6634] sys.exit() called from threads other than the main one: undocumented behaviour
by Jan-Philip Gehrcke Feb. 11, 2015

Feb. 11, 2015

Jan-Philip Gehrcke added the comment: Martin, I very much like the order you suggested, thanks. I did not feel confident enough for re-structuring the entire entry. So, can we agree on using that for Python 2.7? Is there a consensus regarding the approach to take for Python 3.5? Except from Martin there was no feedback on the patch. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue6634> _______________________________________

1 0

[issue22883] Get rid of references to PyInt in Py3 sources
by Serhiy Storchaka Feb. 10, 2015

Feb. 10, 2015

Changes by Serhiy Storchaka <storchaka(a)gmail.com>: ---------- assignee: -> docs@python components: +Documentation -Extension Modules, Interpreter Core nosy: +docs@python _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue22883> _______________________________________

1 0

[issue12954] Multiprocessing logging under Windows
by paul j3 Feb. 10, 2015

Feb. 10, 2015

New submission from paul j3 <ajipanca(a)gmail.com>: The Windows programming guidelines for the multiprocessing module documentation should include a warning that any logging initialization should be protected by the 'if __name__' block. Otherwise you will get duplicate logging entries for the child processes. This is because the multiprocessing.forking.prepare() function explicitly calls log_to_stderr(), and may implicitly do so again when it imports the parent module, resulting in duplicate logging handlers. ---------- assignee: docs@python components: Documentation messages: 143815 nosy: docs@python, paul.j3 priority: normal severity: normal status: open title: Multiprocessing logging under Windows _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue12954> _______________________________________

4 9

Not able to download documentation
by v Sugumar Feb. 10, 2015

Feb. 10, 2015

Hello sir, >From yesterday I am trying to download the documentation from https://docs.python.org/3/download.html But I am getting a page for found error at. https://docs.python.org/3/archives/python-3.4.3rc1-docs-pdf-letter.zip Thanks, v.sugumar

1 0

[issue13407] tarfile doesn't support multistream bzipped tar files
by Serhiy Storchaka Feb. 10, 2015

Feb. 10, 2015

Serhiy Storchaka added the comment: The tarfile module documentation needs a note similar to issue1625 which would warn about the lack of supporting some files and suggest a workaround. ---------- assignee: -> docs@python components: +Documentation nosy: +docs@python, nadeem.vawda, serhiy.storchaka priority: normal -> high stage: -> needs patch status: pending -> open title: tarfile.getnames misses members again -> tarfile doesn't support multistream bzipped tar files versions: -Python 3.2 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue13407> _______________________________________

1 0

Python Documentation Download Issue
by Kevin Bjorn Umali Feb. 10, 2015

Feb. 10, 2015

Hello, I'd like to report that the download links for the Python 3.4.3rc1 (found in https://docs.python.org/3/download.html) are not working. I always get a 404 response regardless of what download link I click. -- Kevin Bjorn V. Umali (+63)9178014406

1 0

Error Report: Python 3 Doc PDF Download Problem
by Gmail Feb. 9, 2015

Feb. 9, 2015

Hi, Today I tried to download the Python 3 Doc from this page https://docs.python.org/3/download.html <https://docs.python.org/3/download.html>. I clicked on PDF (A4 paper size) Packed as .zip as shown in the screenshot below, but the link directs me to a 404 not found page. Could you please help me solve this problem? Thank you. Nathaniel Suen

1 0

[issue6634] sys.exit() called from threads other than the main one: undocumented behaviour
by Martin Panter Feb. 9, 2015

Feb. 9, 2015

Martin Panter added the comment: If it were me, I’d drop the Notes and Warnings (never been a fan), and put Thing #2 first, and then Thing #1. Maybe something like ''' sys.exit([arg]) Exit from Python. . . . and it is possible to intercept the exit attempt at an outer level. When called from a thread other than the main thread, this causes the thread to exit silently instead, and is equivalent to calling :func:`thread.exit`. The optional argument *arg* can be an integer giving the exit status (defaulting to zero). Passing ``None`` is equivalent to passing zero. Any other object is printed to `stderr` and results in an exit status of 1. In particular, ``sys.exit("some error message")`` is a quick way to exit a program when an error occurs. When called from a thread other than the main thread, nothing is printed and the argument is ignored. An exit status of zero is considered “successful termination” and any nonzero status is considered “abnormal termination” . . . Unix programs generally use 2 for command line syntax errors and 1 for all other kinds of errors. ''' ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue6634> _______________________________________

1 0

[issue6634] sys.exit() called from threads other than the main one: undocumented behaviour
by Jan-Philip Gehrcke Feb. 9, 2015

Feb. 9, 2015

Jan-Philip Gehrcke added the comment: I'd love to find an agreement here. I think we are quite close to getting this closed, so further input is very welcome. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue6634> _______________________________________

1 0

(no subject)
by Javokhir Kudratov Feb. 9, 2015

Feb. 9, 2015

I have a problem with downloading. I can't download any kind of docs.

1 0