On Thu, Jun 21, 2012 at 9:26 PM, Christian Heimes <li...@cheimes.de> wrote: > BTW Is there a better way than raise OSError(errno.ELOOP, > os.strerror(errno.ELOOP), filename) to raise a correct OSError with > errno, errno message and filename? A classmethod like > "OSError.from_errno(errno, filename=None) -> proper subclass auf OSError > with sterror() set" would reduce the burden for developers. PEP mentions > the a similar idea at > http://www.python.org/dev/peps/pep-3151/#implementation but this was > never implemented.
According to the C code, it should be working at least for recognised errno values: http://hg.python.org/cpython/file/009ac63759e9/Objects/exceptions.c#l890 I can't get it to trigger properly in my local build, though :( Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
