Mailman 3 February 2015 - docs

[issue6634] sys.exit() called from threads other than the main one: undocumented behaviour
by Antoine Pitrou 03 Feb '15

03 Feb '15

Antoine Pitrou added the comment: I'm not sure what the doc patch achieves. It only states more verbosely what is already said in the current version. Also, warnings are really for important issues (such as security issues); using them too liberally is a disservice to the reader. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue6634> _______________________________________

1 0

[issue13322] buffered read() and write() does not raise BlockingIOError
by Martin Panter 03 Feb '15

03 Feb '15

Martin Panter added the comment: I’m adding nonblock-none.patch, which changes all the simple buffered read methods to return None when there is no non-blocking data available. I’d be interested to see if other people thought this was a sensible change. * Documented existing behaviour of C “io” module buffered read(), readinto/1() returning None * io.BufferedIOBase.read() and io.FileIO.readall() doc strings already mention returning None * Removed false claims of buffered reads returning short for interactive streams, sockets and pipes * Fixed _pyio return values to match C “io” module returning None * Fixed BufferedIOBase.readinto/1() implementation to handle read/1() returning None * Changed buffered read1() and peek() to return None ---------- Added file: http://bugs.python.org/file37995/nonblock-none.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue13322> _______________________________________

1 0

[issue6634] sys.exit() called from threads other than the main one: undocumented behaviour
by Martin Panter 02 Feb '15

02 Feb '15

Martin Panter added the comment: New patches look fine. BTW SystemExit.code is also documented at <https://docs.python.org/dev/library/exceptions.html#SystemExit>. ---------- _______________________________________ 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 02 Feb '15

02 Feb '15

Changes by Jan-Philip Gehrcke <jgehrcke(a)gmail.com>: Added file: http://bugs.python.org/file37990/issue6634_py27.patch _______________________________________ 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 02 Feb '15

02 Feb '15

Changes by Jan-Philip Gehrcke <jgehrcke(a)gmail.com>: Removed file: http://bugs.python.org/file37983/issue6634_py27.patch _______________________________________ 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 02 Feb '15

02 Feb '15

Jan-Philip Gehrcke added the comment: > Regarding the documentation patch: I like to start sentences > with a capital letter. Perhaps change it to start > “Calling :func:`exit` only terminates . . .”. Thanks for feedback. Have now used "Invocation of ...." to not repeat "call*" in the sentence, because I left the "when called from the main thread" part unchanged. Okay? > With the code change patch, it might be neater to use > the SystemExit.code attribute rather than e.args[0]. Oh, thanks. Was not aware of the existence of the `code` attribute. If anyone else was wondering: existence and behavior are defined in Objects/exceptions.c via `static PyMemberDef SystemExit_members[]` and via `static int SystemExit_init()`. It is populated upon construction of a SystemExit instance: Py_CLEAR(self->code); if (size == 1) self->code = PyTuple_GET_ITEM(args, 0); else /* size > 1 */ self->code = args; Hence, the translation from arguments to exit code considers *all* arguments. I adjusted the patch to use the `code` attribute. ---------- Added file: http://bugs.python.org/file37989/issue6634_py35.patch _______________________________________ 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 02 Feb '15

02 Feb '15

Changes by Jan-Philip Gehrcke <jgehrcke(a)gmail.com>: Removed file: http://bugs.python.org/file37988/issue6634_py35.patch _______________________________________ 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 02 Feb '15

02 Feb '15

Changes by Jan-Philip Gehrcke <jgehrcke(a)gmail.com>: Added file: http://bugs.python.org/file37988/issue6634_py35.patch _______________________________________ 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 02 Feb '15

02 Feb '15

Changes by Jan-Philip Gehrcke <jgehrcke(a)gmail.com>: Removed file: http://bugs.python.org/file37986/issue6634_py35.patch _______________________________________ 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 Martin Panter 02 Feb '15

02 Feb '15

Martin Panter added the comment: Regarding the documentation patch: I like to start sentences with a capital letter. Perhaps change it to start “Calling :func:`exit` only terminates . . .”. With the code change patch, it might be neater to use the SystemExit.code attribute rather than e.args[0]. ---------- nosy: +vadmium _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue6634> _______________________________________

1 0