[issue44709] [3.7] Popen Control Characters in stdout affect shell session

New submission from San : I was trying to wrap an old game server executable with a built-in console using Popen. class ServerWrapper(Thread): def __init__(self, pathToExecutable: str, statusMonitor: Popen = None, active: bool = False): super().__init__

[issue44709] [3.7] Popen Control Characters in stdout affect shell session

San added the comment: I get your point. But I thought setting 'stdout=PIPE' should not send the stdout directly to the terminal but rather through the pipe first?! Also what you're saying seems to contradict that this doesn't happen if I don't set the encoding an

[issue44709] [3.7] Popen Control Characters in stdout affect shell session

San added the comment: I just realised that this is not a problem of python but rather a problem of the shell that I was using. I was testing the io in a different environment. Now I retried in the same environment that the wrapper was operating and the behaviour is the same using io

[issue40034] cgi.parse() does not work with multipart POST requests.

New submission from San : The cgi.parse stdlib function works in most cases but never works when given a multipart/form-data POST request because it does not set up pdict in a way cgi.parse_multipart() likes (boundary as bytes (not str) and including content length). $ pwd /tmp $ $ /tmp

[issue40034] cgi.parse() does not work with multipart POST requests.

Change by San : -- keywords: +patch pull_requests: +18492 stage: -> patch review pull_request: https://github.com/python/cpython/pull/19130 ___ Python tracker <https://bugs.python.org/issu

[issue14204] Support for the NPN extension to TLS/SSL

Changes by Sidney San Martín : -- nosy: +ssm ___ Python tracker <http://bugs.python.org/issue14204> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue14652] Better error messages for wsgiref validator failures

New submission from Sidney San Martín : wsgiref’s validation middleware is missing messages for many of its assertions, and its docstring doesn’t reflect read() now requiring an argument (said that it took an optional argument). Here’s a patch to add some and update the comment

[issue14835] plistlib: output empty elements correctly

New submission from Sidney San Martín : plistlib’s output is currently byte-for-byte identical to Apple’s, except arrays and dictionaries are stored with self-closing tags (e.g. '') and plistlib outputs empty tags with a newline (e.g. '\n'). This tiny patch makes its out

[issue14652] Better error messages for wsgiref validator failures

Sidney San Martín added the comment: Thanks Jeff, I’m actually a relatively new Python developer and got the impression that it was best practice to always use a tuple for string formatting, for consistency. Here’s an updated patch which drops the tuples for those cases. -- Added

[issue14835] plistlib: output empty elements correctly

Sidney San Martín added the comment: Hynek: Here you go! Ronald: Emailed it in on Friday. -- Added file: http://bugs.python.org/file25734/plistlib_empty_element_test.patch ___ Python tracker <http://bugs.python.org/issue14

[issue14835] plistlib: output empty elements correctly

Sidney San Martín added the comment: Thanks Hynek, awesome! It looks like it’s in now. -- ___ Python tracker <http://bugs.python.org/issue14835> ___ ___ Pytho