RetroSearch Browse

Tue Apr 24 18:56:50 CEST 2012 · https://mail.python.org/pipermail/python-dev/2012-April/119006.html

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

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2012-April/119006.html below:

[Python-Dev] [Python-checkins] peps: Note that ImportError will no longer be raised due to a missing init.py

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2012-April/119006.html below:

[Python-Dev] [Python-checkins] peps: Note that ImportError will no longer be raised due to a missing __init__.py

[Python-Dev] [Python-checkins] peps: Note that ImportError will no longer be raised due to a missing init.py