[issue17650] There is no exception correspond to errno EROFS

Andrew Svetlov added the comment: Ok. Antoine's comment is clean. Let's close the issue. -- status: pending -> closed ___ Python tracker ___ _

[issue17650] There is no exception correspond to errno EROFS

Antoine Pitrou added the comment: A bit in detail: - ENOTCONN is a programming error, so there's no use actually catching it (you should fix the bug instead when you encounter it) - EINVAL could be a candidate, but unfortunately it would clash quite nastily with ValueError and lead to confusion

[issue17650] There is no exception correspond to errno EROFS

Georg Brandl added the comment: Antoine will have to decide on this, but IMO now that we released the PEP 3151 set in Python 3.3, we should not continue adding new builtin exceptions in every release. -- ___ Python tracker

[issue17650] There is no exception correspond to errno EROFS

Andrew Svetlov added the comment: Sorry for reopening. Do you really sure that ENOTCONN and EINVAL doesn't worth to have separate sublasses? The same question about Not Supported family. I don't force to make new exception classes, just like to figure out the status quo. If we decide to kee

[issue17650] There is no exception correspond to errno EROFS

Changes by Georg Brandl : -- resolution: -> wont fix status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue17650] There is no exception correspond to errno EROFS

Changes by Andrew Svetlov : -- nosy: +asvetlov ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue17650] There is no exception correspond to errno EROFS

Changes by Andrey Tykhonov : -- components: +Library (Lib) type: -> enhancement versions: +Python 3.4 ___ Python tracker ___ ___ Pyth

[issue17650] There is no exception correspond to errno EROFS

Antoine Pitrou added the comment: The rationale for not creating dedicated exception classes is that those errors are not common enough. Since the range of possible errno values is basically unbounded (each system can create their own system-specific errors), trying to cover them all is a losi

[issue17650] There is no exception correspond to errno EROFS

Andrey Tykhonov added the comment: Also: errno.EXDEV in Lib/distutils/file_util.py errno.ENOTCONN in Lib/poplib.py errno.EINVAL in Lib/subprocess.py errno.ENOTCONN in Lib/smtpd.py, Lib/ssl.py, Lib/imaplib.py errno.EOPNOTSUPP, errno.ENOTSUP, errno.ENOTSUP, errno.ENODATA in Lib/shutil.py -

[issue17650] There is no exception correspond to errno EROFS

New submission from Андрій Тихонов: I found errno.EROFS in Lib/mailbox.py but didn't find exception correspond to this errno. Is it need to be created? -- messages: 186185 nosy: pitrou, Андрій.Тихонов priority: normal severity: normal status: open title: There is no exception correspon