[Python-Dev] PEP 328: path (original) (raw)
Guido van Rossum guido at python.org
Sun Apr 4 12:43:26 EDT 2004
- Previous message: [Python-Dev] PEP 328: __path__
- Next message: [Python-Dev] PEP 328: __path__
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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 forimport
, there is no longer a need for_path_
, and it is now officially deprecated. In Python 2.4 and 2.5, changing_path_
raisesPendingDeprecationWarning
. In Python 2.6,_path_
becomes a read-only attribute. In the presence ofabsoluteimport
or with a relative import,_path_
is ignored.
Uh? Maybe you should have some coffee and then try again.
path has nothing to do with relative import. When I say "import foo.bar" then bar is searched for in foo.path. path defines which directories comprise the package contents, nothing more or less.
--Guido van Rossum (home page: http://www.python.org/~guido/)
- Previous message: [Python-Dev] PEP 328: __path__
- Next message: [Python-Dev] PEP 328: __path__
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]