Message28851
Trying to import from a module using dotted import syntax produces
this exception:
ValueError: Relative importpath too deep
This behavior has been confirmed on Mac OS X 10.4 using the Python
2.5b1 disk image; and on CentOS 4 using the Python 2.5b1 source
tarball.
The exception is raised regardless of whether the PYTHONPATH
environment variable can see the toplevel directory of the package
being tested; regardless of whether the import is performed from an
interactive Python session or from a script invoked from the command
line; and regardless of whether the main script starts with
from __future__ import absolute_import
To test, I tried to re-create the package structure used as an example
in PEP 328. (See attachments.)
Most of the files were empty, except moduleX.py and moduleY.py:
#moduleX.py:
from __future__ import absolute_import
from .moduleY import spam
#moduleY.py:
spam = "spam"
According to the PEP, if should be possible to import moduleX without
error. But I get the above exception whenever I try to import moduleX
or to run it from the command line.
$ python2.5 moduleX.py
Traceback (most recent call last):
File "moduleX.py", line 3, in <module>
from .moduleY import spam
ValueError: Relative importpath too deep
Is this a usage/documentation error?
|
|
Date |
User |
Action |
Args |
2007-08-23 14:40:44 | admin | link | issue1510172 messages |
2007-08-23 14:40:44 | admin | create | |
|