New submission from Serhiy Storchaka:
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.
----------
components: IO
messages: 209109
nosy: benjamin.peterson, hynek, pitrou, serhiy.storchaka, stutzbach
priority: normal
severity: normal
status: open
title: open() exception doesn't contain file name on Windows
type: behavior
versions: Python 3.3
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue20384>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
