[issue10715] uninformative error message

Eric Smith added the comment: Here's a code snippet that shows the problem: >>> import subprocess >>> subprocess.Popen(['foo']) Traceback (most recent call last): File "", line 1, in File "/usr/lib/python2.5/subprocess.py", line 593, in __init__ errread, errwrite) File "/usr/lib/pyth

[issue10715] uninformative error message

Eric Smith added the comment: Because you're sending email as HTML, the message shows up both as plain text and as an attachment. It's the attachments that are being removed. If you could, please stop sending HTML email. -- ___ Python tracker

[issue10715] uninformative error message

Changes by Eric Smith : Removed file: http://bugs.python.org/file20126/unnamed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubs

[issue10715] uninformative error message

Phillip M. Feldman added the comment: Why was this removed? On Mon, Dec 20, 2010 at 8:30 PM, Alexander Belopolsky < rep...@bugs.python.org> wrote: > > Changes by Alexander Belopolsky : > > > Removed file: http://bugs.python.org/file20125/unnamed > > ___ > Py

[issue10715] uninformative error message

Changes by Alexander Belopolsky : Removed file: http://bugs.python.org/file20125/unnamed ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue10715] uninformative error message

Phillip M. Feldman added the comment: I eventually determined that a call to `subprocess.Popen` was responsible for the message, but could have determined this much more quickly if the message had included the name of the file that could not be opened (executed). Phillip On Mon, Dec 20, 2010 a

[issue10715] uninformative error message

Changes by Éric Araujo : -- components: +IO nosy: +eric.araujo versions: +Python 2.7, Python 3.1, Python 3.2 -Python 2.6 ___ Python tracker ___ __

[issue10715] uninformative error message

Eric Smith added the comment: Operating systems also return this errno for many, many things unrelated to files. So while we might be able to fix this in some specific cases, in general it's not possible to add file names to all errors. Once we know your specific case we can see if it's fixab

[issue10715] uninformative error message

Amaury Forgeot d'Arc added the comment: Normally the filename is part of the error message, as you can see below. It's possible that some operations omit it, though. Which function were you calling? >>> open('foo') Traceback (most recent call last): File "", line 1, in IOError: [Errno 2] No

[issue10715] uninformative error message

New submission from Phillip Feldman : The error message "OSError: [Errno 2] No such file or directory" would be far more helpful if it specified the name of the file or directory that cannot be found. -- messages: 124108 nosy: Phillip.M.Feldman priority: normal severity: normal status: