[issue8373] socket: AF_UNIX socket paths not handled according to PEP 383

Antoine Pitrou added the comment: Patch committed in 3.3 (default branch), thank you! -- nosy: +pitrou resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed versions: +Python 3.3 -Python 3.1, Python 3.2 ___ Python tra

[issue8373] socket: AF_UNIX socket paths not handled according to PEP 383

Roundup Robot added the comment: New changeset 1f23bb74f4bc by Antoine Pitrou in branch 'default': Issue #8373: The filesystem path of AF_UNIX sockets now uses the filesystem http://hg.python.org/cpython/rev/1f23bb74f4bc -- nosy: +python-dev ___ Pyth

[issue8373] socket: AF_UNIX socket paths not handled according to PEP 383

David Watson added the comment: One of the tests got broken by the removal of sys.setfilesystemencoding(). Replaced it. -- Added file: http://bugs.python.org/file18853/af_unix-pep383-docs-tests-3.2-2.diff ___ Python tracker

[issue8373] socket: AF_UNIX socket paths not handled according to PEP 383

Changes by David Watson : Added file: http://bugs.python.org/file18852/af_unix-pep383-3.2-without-linux-unterminated.diff ___ Python tracker ___ _

[issue8373] socket: AF_UNIX socket paths not handled according to PEP 383

Changes by David Watson : Added file: http://bugs.python.org/file18851/af_unix-pep383-3.2-with-linux-unterminated.diff ___ Python tracker ___

[issue8373] socket: AF_UNIX socket paths not handled according to PEP 383

David Watson added the comment: Updated the patches for Python 3.2 - these are now simpler as they do not support bytearray arguments, as these are no longer used for filenames (the existing code does not support bytearrays either). I've put the docs and tests in one patch, and made separate pa

[issue8373] socket: AF_UNIX socket paths not handled according to PEP 383

Changes by Antoine Pitrou : -- nosy: +haypo, loewis priority: -> normal stage: -> patch review versions: -Python 3.3 ___ Python tracker ___

[issue8373] socket: AF_UNIX socket paths not handled according to PEP 383

Changes by David Watson : Added file: http://bugs.python.org/file16885/af_unix-pep383-doc.diff ___ Python tracker ___ ___ Python-bugs-list mail

[issue8373] socket: AF_UNIX socket paths not handled according to PEP 383

Changes by David Watson : Added file: http://bugs.python.org/file16884/test-new.diff ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue8373] socket: AF_UNIX socket paths not handled according to PEP 383

Changes by David Watson : Added file: http://bugs.python.org/file16883/test-existing.diff ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue8373] socket: AF_UNIX socket paths not handled according to PEP 383

David Watson added the comment: This patch does the same thing without fixing issue #8372 (not that I'd recommend that, but it may be easier to review). -- Added file: http://bugs.python.org/file16882/af_unix-pep383-no-8372-fix.diff ___ Python tracke

[issue8373] socket: AF_UNIX socket paths not handled according to PEP 383

New submission from David Watson : In 3.x, the socket module assumes that AF_UNIX addresses use UTF-8 encoding - this means, for example, that accept() will raise UnicodeDecodeError if the peer socket path is not valid UTF-8, which could crash an unwary server. Python 3.1.2 (r312:79147, Mar 23 2