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 ncoghlan
Recipients aivazis, brett.cannon, eric.araujo, loewis, ncoghlan
Date 2010-11-19.15:50:58
SpamBayes Score 2.63808e-07
Marked as misclassified No
Message-id <1290181860.34.0.164226789518.issue4476@psf.upfronthosting.co.za>
In-reply-to
Content
No. Once you start shadowing standard library modules, all bets are off as to what will and won't work. It's one of the reasons we need to be somewhat careful with the naming of new standard library modules.

I'm mildly curious as to why 2.7 didn't also throw ImportError*, but given the description, I don't consider it incorrect behaviour that this scenario broke in 3.x.

*Off the top of my head, I would guess it is due to the change in initialisation order needed to bootstrap the new IO stack in 3.x, but it would take a bit of investigation to confirm that
History
Date User Action Args
2010-11-19 15:51:00ncoghlansetrecipients: + ncoghlan, loewis, brett.cannon, aivazis, eric.araujo
2010-11-19 15:51:00ncoghlansetmessageid: <1290181860.34.0.164226789518.issue4476@psf.upfronthosting.co.za>
2010-11-19 15:50:58ncoghlanlinkissue4476 messages
2010-11-19 15:50:58ncoghlancreate