This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author serhiy.storchaka
Recipients benjamin.peterson, hynek, pitrou, serhiy.storchaka, stutzbach
Date 2014-01-24.19:34:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1390592079.62.0.820816905232.issue20384@psf.upfronthosting.co.za>
In-reply-to
Content
On Linux for 2.7, 3.3 and 3.4 the open of non-existing file raises an exception which contains file name.

Python 2.7:

>>> open('non-existing', 'rb')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
IOError: [Errno 2] No such file or directory: 'non-existing'
>>> import io
>>> io.open('non-existing', 'rb')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
IOError: [Errno 2] No such file or directory: 'non-existing'

Python 3.3 and 3.4:

>>> open('non-existing', 'rb')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
FileNotFoundError: [Errno 2] No such file or directory: 'non-existing'

On Windows for 2.7 and 3.4 raised exception also contains file name. But on 3.3 error message is only "[Errno 2] No such file or directory" and doesn't contains file name.

This change affects tests. test_tarfile failed on all Windows buildbots for 3.3.

http://buildbot.python.org/all/builders/x86%20Windows7%203.3/builds/1252/steps/test/logs/stdio

I suppose this is 3.3 bug.
History
Date User Action Args
2014-01-24 19:34:39serhiy.storchakasetrecipients: + serhiy.storchaka, pitrou, benjamin.peterson, stutzbach, hynek
2014-01-24 19:34:39serhiy.storchakasetmessageid: <1390592079.62.0.820816905232.issue20384@psf.upfronthosting.co.za>
2014-01-24 19:34:39serhiy.storchakalinkissue20384 messages
2014-01-24 19:34:38serhiy.storchakacreate