homepage

Logged In: YES 
user_id=1038590
All that said, PEP 328 currently says that "from ...sys
import path" should be legal from moduleX in the example.
I tried it, and it currently fails - the ValueError gets
raised as soon as the number of dots in the relative path
exceeds the number of dots in __name__, instead of treating
a single excess dot as requesting an absolute import
instead. (All of the other examples in the PEP work as
specified when moduleX and subpackage1 are imported rather
than executed directly)
I believe fixing this would also fix Mitch's problem - an
explicit relative import from __main__ would be treated as a
top level import.
I also have an idea regarding the -m switch that I will
raise on python-dev.