[issue26493] Bad formatting in WinError 193 when using subprocess.check_call

Raúl Núñez de Arenas added the comment: That's the kind of patch I assumed was created for the Windows part, Berker, that's why I reopened the issue. Thanks for the information. -- ___ Python tracker <https://bugs.python.org/issue26

[issue26493] Bad formatting in WinError 193 when using subprocess.check_call

Raúl Núñez de Arenas added the comment: Hi Steve :) I assumed that the issue was solved, that's why I warned, in case a patch was applied and it didn't work. When I did read "I suggest to only call reformat_strerror() when an user complains", I supposed a patch was ready O:) No b

[issue26493] Bad formatting in WinError 193 when using subprocess.check_call

Raúl Núñez de Arenas added the comment: I'm sorry to say that this still happens in Python 3.7.0... -- ___ Python tracker <https://bugs.python.org/issue26

[issue26493] Bad formatting in WinError 193 when using subprocess.check_call

Raúl Núñez de Arenas added the comment: Thanks for the information, Eryk, I've read the blog. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/i

[issue26493] Bad formatting in WinError 193 when using subprocess.check_call

New submission from Raúl Núñez de Arenas: Python 3.5.1 x64 @ Windows 10 x64 The error message in the traceback for OSError/WinError 193 has bad formatting and the offending file name is not printed. For example, this code: import subprocess testfile = open('testfile.notexecutable', 'wb

[issue26401] Error in documentation for "compile" built-in function

Raúl Núñez de Arenas added the comment: Thanks to you, Berker, and SilentGhost, for applying and preparing the patch! -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/i

[issue26401] Error in documentation for "compile" built-in function

Raúl Núñez de Arenas added the comment: I checked the Mercurial repository directly, and the change was introduced in 2014: http://bugs.python.org/issue22215 So, yes, looks like a 3.5 change and the versionchanged note suggested by Berker is a great idea

[issue26401] Error in documentation for "compile" built-in function

Raúl Núñez de Arenas added the comment: I checked the sources at github and the change was introduced back in 2010, if I recall correctly, so maybe this change happened in 3.2? I can check again and try to determine the exact date and if at all possible the version

[issue26401] Error in documentation for "compile" built-in function

New submission from Raúl Núñez de Arenas: According to the documentation, if the 'compile' built-in function encounters NUL bytes in the compiled source, it raises TypeError, but this is not true: >>> source = '\u' >>> compile(source, '', 'single') Traceback (most recent

[issue26311] Typo in documentation for xml.parsers.expat

Raúl Núñez de Arenas added the comment: My pleasure :) -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue26311> ___ ___ Python-bugs-

[issue26311] Typo in documentation for xml.parsers.expat

New submission from Raúl Núñez de Arenas: At https://docs.python.org/3.5/library/pyexpat.html#module-xml.parsers.expat.model the docs say "Content modules are described using nested tuples. It should say "Content models are described using nested tuples." I've checked docs for