[issue4476] compileall fails if current dir has a "types" package

[Nick Coghlan]

Nick Coghlan <ncoghlan at gmail.com> added the comment:

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

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue4476>
_______________________________________