Mailman 3 April 2016 - docs

[issue26703] Socket state corrupts when original socket object goes out of scope in a different thread
by Antoine Pitrou 07 Apr '16

07 Apr '16

Antoine Pitrou added the comment: The general answer here is you should avoid mixing calls to different abstraction layers. Either use only the file descriptor or only the socket object. This is not limited to lifetime issues, other issues can occur. For example, setting a timeout on a socket puts the underlying file descriptor in non-blocking mode. So code using the file descriptor can fail with EAGAIN. If you really want to use *both* a file descriptor and a socket object, you can use os.dup() on the file descriptor, so that the OS resources are truly independent. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue26703> _______________________________________

1 0

[issue26703] Socket state corrupts when original socket object goes out of scope in a different thread
by Martin Panter 07 Apr '16

07 Apr '16

Martin Panter added the comment: Yes, I think this is the expected behaviour, and I can’t think of any improvements that could be made. If you call fileno(), you have to ensure that you don’t close the file descriptor until you have finished using it. It is a bit like accessing memory after it has been freed. Python doesn’t make raw memory addresses easily accessible, but it does make fileno() accessible without much protection. Perhaps there is some confusion about the term socket. Normally (without using the fileno=... parameter), Python’s socket() constructor does two things. First, it creates a new OS socket using the socket() system call (or Winsock equivalent), which returns a file descriptor or handle (an integer). Then, it creates a Python socket object, which wraps the file descriptor. When you use socket(fileno=...), only the second step is taken. You get a _new_ socket object, which wraps the given existing OS socket file descriptor. So when it says “the same socket”, I think it means the same OS-level socket. It still creates a new Python object. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue26703> _______________________________________

1 0

[issue26703] Socket state corrupts when original socket object goes out of scope in a different thread
by JoshN 07 Apr '16

07 Apr '16

JoshN added the comment: I do understand that the docs are a bit strange on the issue. For example, actually testing the line you referenced ("...fileno will return the same socket and not a duplicate.") by creating 2 sockets and testing sameness with the 'is' operator returns false. I tried to trim the example code as much as possible - I did test disabling the garbage collector, playing with inheritance, etc, but trimmed them out as they didn't have any effect on my system. I think my main issue was, when this occurs, the socket 'breaks' as you mentioned instead of closing. Was almost sure it was a bug. Using detach works for this UDP example, but I wasn't sure if detaching the socket actually closes it (e.g. in a stream oriented connection). So this is considered normal behavior then? ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue26703> _______________________________________

1 0

[issue26703] Socket state corrupts when original socket object goes out of scope in a different thread
by Martin Panter 07 Apr '16

07 Apr '16

Martin Panter added the comment: Also, if you enable warnings (e.g. python -Wall), you should see that the socket is being closed: -c:22: ResourceWarning: unclosed <socket.socket fd=3, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=0, laddr=('0.0.0.0', 8080)> ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue26703> _______________________________________

1 0

[issue26703] Socket state corrupts when original socket object goes out of scope in a different thread
by Martin Panter 07 Apr '16

07 Apr '16

Martin Panter added the comment: The documentation already says “Sockets are automatically closed when they are garbage-collected”. If for some reason you want to release a socket object but keep the file descriptor open, I suggest socket.detach(). Otherwise, pass the original socket, not the fileno. I think this is at best a documentation issue, if you have any suggestions. ---------- assignee: -> docs@python components: +Documentation -IO nosy: +docs@python, martin.panter type: crash -> behavior _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue26703> _______________________________________

1 0

[issue10796] Improve doc for readline.set_completer_delims()
by Martin Panter 06 Apr '16

06 Apr '16

Martin Panter added the comment: My update includes a new section called Completion, with the following text: By default, Readline is set up to be used by “rlcompleter” to complete Python identifiers for the interactive interpreter. If the “readline” module is to be used with a custom completer, a different set of word delimiters should be set. I hope that is enough to call this fixed :) ---------- resolution: -> fixed stage: needs patch -> resolved status: open -> closed versions: +Python 3.5, Python 3.6 -Python 3.2, Python 3.3, Python 3.4 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue10796> _______________________________________

1 0

[issue26696] Document collections.abc.ByteString
by Brett Cannon 05 Apr '16

05 Apr '16

Changes by Brett Cannon <brett(a)python.org>: ---------- assignee: -> docs@python components: +Documentation -Library (Lib) nosy: +docs@python _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue26696> _______________________________________

1 0

[issue10796] Improve doc for readline.set_completer_delims()
by Roundup Robot 05 Apr '16

05 Apr '16

Roundup Robot added the comment: New changeset 6137c46cb8df by Martin Panter in branch '2.7': Issue #6953: Rearrange and expand Readline module documentation https://hg.python.org/cpython/rev/6137c46cb8df New changeset b1acd6cf15b6 by Martin Panter in branch '3.5': Issue #6953: Rearrange and expand Readline module documentation https://hg.python.org/cpython/rev/b1acd6cf15b6 ---------- nosy: +python-dev _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue10796> _______________________________________

1 0

[issue9694] argparse required arguments displayed under "optional arguments"
by Martin Panter 05 Apr '16

05 Apr '16

Martin Panter added the comment: Posting argparse_option.v2.patch, which is minimally complete version of Ryan’s patch. I have dropped all the nonessential code and documentation tweaks. I also added a What’s New entry. I’d like to know if people think this is the right direction to move in. ---------- versions: -Python 2.7, Python 3.5 Added file: http://bugs.python.org/file42370/argparse_option.v2.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue9694> _______________________________________

1 0

[issue26479] Init documentation typo "may be return" > "may NOT be returned"
by Samuel Colvin 03 Apr '16

03 Apr '16

New submission from Samuel Colvin: https://docs.python.org/3/reference/datamodel.html#object.__init__ "no non-None value may be returned by __init__();" should read "no non-None value may *not* be returned by __init__();" ---------- assignee: docs@python components: Documentation messages: 261185 nosy: Samuel Colvin, docs@python priority: normal severity: normal status: open title: Init documentation typo "may be return" > "may NOT be returned" versions: Python 3.4, Python 3.5, Python 3.6 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue26479> _______________________________________

2 2