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

[Raúl Núñez de Arenas]

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/issue26493>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Raúl Núñez de Arenas]

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 big deal, I can deal with that particular error in my code.

--

___
Python tracker 
<https://bugs.python.org/issue26493>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Raúl Núñez de Arenas]

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/issue26493>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Raúl Núñez de Arenas]

Raúl Núñez de Arenas added the comment:

Thanks for the information, Eryk, I've read the blog.

--

___
Python tracker 
<http://bugs.python.org/issue26493>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Raúl Núñez de Arenas]

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')
testfile.close()
subprocess.check_call(['testfile.notexecutable'])


produces this output:

Traceback (most recent call last):
  File "test.py", line 6, in 
subprocess.check_call(['testfile.notexecutable'])
  File "C:\Program Files\Python35\lib\subprocess.py", line 579, in check_call
retcode = call(*popenargs, **kwargs)
  File "C:\Program Files\Python35\lib\subprocess.py", line 560, in call
with Popen(*popenargs, **kwargs) as p:
  File "C:\Program Files\Python35\lib\subprocess.py", line 950, in __init__
restore_signals, start_new_session)
  File "C:\Program Files\Python35\lib\subprocess.py", line 1220, in 
_execute_child
startupinfo)
OSError: [WinError 193] %1 is not a valid Win32 application


Please note the "%1 is not a valid..." on the last line. Instead of the "%1" 
placeholder, the filename ("testfile.notexecutable") should appear instead.

Thanks :)

--
messages: 261262
nosy: Raúl Núñez de Arenas
priority: normal
severity: normal
status: open
title: Bad formatting in WinError 193 when using subprocess.check_call
versions: Python 3.5

___
Python tracker 
<http://bugs.python.org/issue26493>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Raúl Núñez de Arenas]

Raúl Núñez de Arenas added the comment:

Thanks to you, Berker, and SilentGhost, for applying and preparing the patch!

--

___
Python tracker 
<http://bugs.python.org/issue26401>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Raúl Núñez de Arenas]

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!

--

___
Python tracker 
<http://bugs.python.org/issue26401>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Raúl Núñez de Arenas]

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.

--

___
Python tracker 
<http://bugs.python.org/issue26401>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Raúl Núñez de Arenas]

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 call last):
  File "", line 1, in 
ValueError: source code string cannot contain null bytes

It raises ValueError, not TypeError. And IMHO, it's the proper exception to 
raise...

--
assignee: docs@python
components: Documentation
messages: 260613
nosy: Raúl Núñez de Arenas, docs@python
priority: normal
severity: normal
status: open
title: Error in documentation for "compile" built-in function
type: enhancement
versions: Python 3.5

___
Python tracker 
<http://bugs.python.org/issue26401>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Raúl Núñez de Arenas]

Raúl Núñez de Arenas added the comment:

My pleasure :)

--

___
Python tracker 
<http://bugs.python.org/issue26311>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Raúl Núñez de Arenas]

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 version 3.6.0a and the typo is there, too.

--
components: XML
messages: 259873
nosy: Raúl Núñez de Arenas
priority: normal
severity: normal
status: open
title: Typo in documentation for xml.parsers.expat
versions: Python 3.5

___
Python tracker 
<http://bugs.python.org/issue26311>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com