[Python-Dev] PEP 328: __path__

Samuele Pedroni pedronis at bluewin.ch
Sun Apr 4 12:35:28 EDT 2004

At 12:21 04.04.2004 -0400, Aahz wrote:
>I just realized that the new relative import semantics are likely to
>interact oddly with uses of ``__path__``.  I therefore suggest that the
>following text be added to PEP 328, although I'm perfectly happy to
>adopt some other course:
>Between the addition of ``as`` in Python 2.0 and the new syntax &
>semantics for ``import``, there is no longer a need for ``__path__``, and
>it is now officially deprecated.  In Python 2.4 and 2.5, changing
>``__path__`` raises ``PendingDeprecationWarning``.  In Python 2.6,
>``__path__`` becomes a read-only attribute.  In the presence of
>``absolute_import`` or with a relative import, ``__path__`` is ignored.

that's an issue because people use __path__ to spread a package
over many directories and not just in ther relative

Btw I thought (I admit I have not read the PEP) that relative imports are 
an operation over package names

import .c .# in a.b -> a.c

not about concrete directories.


More information about the Python-Dev mailing list