[issue2158] confusing exception when opening a filename with nonprintable characters

[Ronald Oussoren]

Ronald Oussoren <ronaldoussoren at mac.com> added the comment:

AFAIK this is fixed in the trunk, you'll get a message that the filename 
or mode is incorrect (but not which one).

That's the best open() can do because the underlying C API doesn't give 
enough information to decide which argument is unacceptable.

(I'm changing this to the library component instead of the Macintosh one 
because this was a buglet in the platform-independent stdlib).

The trunk was fixed in r61468, that might be a backport candidate, 
adding gregory.p.smith to the nosy list because he commited that 
revision.

----------
components: +Library (Lib) -Macintosh
nosy: +gregory.p.smith, ronaldoussoren

__________________________________
Tracker <report at bugs.python.org>
<http://bugs.python.org/issue2158>
__________________________________