Author mitchchapman
Date 2006-06-21.23:57:31
SpamBayes Score
Marked as misclassified
Logged In: YES 

Hm... but the same error occurs if one tries to import moduleX from an 
interactive Python session, or from a sibling module.

In other words, in 2.5b1 any module which uses relative imports can be used 
only as a fully-qualified member of a package.  It cannot be imported directly 
by a sibling module, and it cannot be used as a main module at all:

$ python2.5 -m package.subpackage1.moduleX
    from .moduleY import spam
ValueError: Relative importpath too deep

Given other efforts (PEP 299; PEP 338) to make it easier to use modules both 
as mainlines and as imports, I still think this is a bug.
Date User Action Args
2007-08-23 14:40:44adminlinkissue1510172 messages
2007-08-23 14:40:44admincreate