A RetroSearch Logo

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

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2012-April/119007.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 [Python-Dev] [Python-checkins] peps: Note that ImportError will no longer be raised due to a missing __init__.pyEric Smith eric at trueblade.com
Tue Apr 24 19:02:30 CEST 2012
> 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"?

Right. If I just install zope.interfaces and no other zope packages, that
shouldn't be an error.

Eric.

More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4