Message181225
Consider the following directory structure:
a-\
__init__.py
b.py
b-|
__init__.py
Now, in Python (I checked 2.7.3 and 3.2.3, haven't seen the issue mentioned anywhere so I suspect it is also in later Pythons), if you import a.b, you always get the package (that is, the b folder), and the module (b.py) is silently ignored. I tested by putting the line """print("I'm a package")""" in a/b/__init__.py and """print("I'm a module")""" in a/b.py.
This becomes a real problem with tools which find modules dynamically, like test harnesses.
I'd expect that in such cases, Python should "avoid the temptation to guess", and raise an ImportError.
Thanks, Shai. |
|
Date |
User |
Action |
Args |
2013-02-02 22:41:08 | shai | set | recipients:
+ shai |
2013-02-02 22:41:08 | shai | set | messageid: <1359844868.64.0.586214844711.issue17108@psf.upfronthosting.co.za> |
2013-02-02 22:41:08 | shai | link | issue17108 messages |
2013-02-02 22:41:08 | shai | create | |
|