➜

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 vstinner
Recipients Arfrever, georg.brandl, larry, python-dev, richard, serhiy.storchaka, vajrasky, vstinner
Date 2014-02-10.10:21:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1392027676.88.0.109958456586.issue20517@psf.upfronthosting.co.za>
In-reply-to
Content 
The family of "PyErr_SetExcFrom..." functions was used when there were various kind of exceptions: select.error, mmap.error, OSError, IOError, socket.error, etc. The "PEP 3151: Reworking the OS and IO exception hierarchy" has been implemented in Python 3.3. I'm not sure that we need such function anymore, a function always raising OSError is probably enough:

"PyErr_SetExcFromWindowsErrWithFilenameObjects" name should be just "PyErr_SetFromWindowsErrWithFilenames". I hate such long names :-(
History
Date User Action Args
2014-02-10 10:21:16vstinnersetrecipients: + vstinner, richard, georg.brandl, larry, Arfrever, python-dev, serhiy.storchaka, vajrasky
2014-02-10 10:21:16vstinnersetmessageid: <1392027676.88.0.109958456586.issue20517@psf.upfronthosting.co.za>
2014-02-10 10:21:16vstinnerlinkissue20517 messages
2014-02-10 10:21:16vstinnercreate