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 pitrou
Recipients Arfrever, brett.cannon, eric.snow, ncoghlan, pitrou, vstinner
Date 2011-10-17.17:17:39
SpamBayes Score 1.2193411e-05
Marked as misclassified No
Message-id <1318871626.3237.6.camel@localhost.localdomain>
In-reply-to <1318870946.5.0.55917483865.issue13192@psf.upfronthosting.co.za>
Content
> Are you suggesting raising the OSError (or something else) rather than
> an ImportError?  If so, would it make sense to chain the exception
> instead.  That way the existing code that expects ImportError
> continues to work

Does any existing code rely on ImportError being raised when there's a
rare OS error of some sort?
History
Date User Action Args
2011-10-17 17:17:40pitrousetrecipients: + pitrou, brett.cannon, ncoghlan, vstinner, Arfrever, eric.snow
2011-10-17 17:17:40pitroulinkissue13192 messages
2011-10-17 17:17:40pitroucreate