Message186073
Like I mentioned on python-dev, it worries me a bit that this could be considered "unexpected", i.e. when there is a conflict between a legitimage attribute member of a module, and a submodule of the same name.
Also, I wonder if this isn't a bigger change to the import mechanism, than simply:
| Another would be
| to always require an 'as' clause in this case, so that you would have
| to write'
| import .foo as foo
which would possibly only require a change to the syntax. |
|
Date |
User |
Action |
Args |
2013-04-05 11:30:23 | kristjan.jonsson | set | recipients:
+ kristjan.jonsson, brett.cannon, pje, methane, eric.snow, pconnell |
2013-04-05 11:30:23 | kristjan.jonsson | set | messageid: <1365161423.56.0.647272469444.issue17636@psf.upfronthosting.co.za> |
2013-04-05 11:30:23 | kristjan.jonsson | link | issue17636 messages |
2013-04-05 11:30:23 | kristjan.jonsson | create | |
|