Chris Rebert <pyb...@rebertia.com> added the comment:
No, it isn't. Changing the `IOError(errno.ENOENT, "...`s to
`FileNotFoundError("...`s would half fix it.
The other half, the `OSError(errno.ENOSYS)`s, has a FIXME for what's the right
error to raise in that case ("no application associated with files of this
type"). I have no idea myself. None of the new PEP 3151 errors apply. Nor did
any of the errnos strictly speaking AFAICT; ENOSYS was the closest
approximation I could find. Thoughts? Custom error class? Different errno?
Something else?
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue3177>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
