[Python-Dev] [Python-checkins] peps: Note that ImportError will no longer be raised due to a missing init.py (original) (raw)
Jim Jewett jimjjewett at gmail.com
Tue Apr 24 18:56:50 CEST 2012
- Previous message: [Python-Dev] [Python-checkins] peps: Note that ImportError will no longer be raised due to a missing __init__.py
- Next message: [Python-Dev] [Python-checkins] peps: Note that ImportError will no longer be raised due to a missing __init__.py
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, Apr 19, 2012 at 18:56, eric.smith wrote:
+Note that an ImportError will no longer be raised for a directory +lacking an
_init_.py
file. Such a directory will now be imported +as a namespace package, whereas in prior Python versions an +ImportError would be raised.
Given that there is no way to modify the path of a namespace package (short of restarting python?), should it be an error if there is exactly one directory?
Or is that just a case of "other tools out there, didn't happen to install them"?
-jJ
- Previous message: [Python-Dev] [Python-checkins] peps: Note that ImportError will no longer be raised due to a missing __init__.py
- Next message: [Python-Dev] [Python-checkins] peps: Note that ImportError will no longer be raised due to a missing __init__.py
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]