brett at python
Apr 19, 2012, 7:59 PM
Post #1 of 5
It's actually an ImportWarning, not Error (or at least that's what I meant
Re: [Python-checkins] peps: Note that ImportError will no longer be raised due to a missing __init__.py
on import-sig). If the module is eventually found then there is no error.
On Thu, Apr 19, 2012 at 18:56, eric.smith <python-checkins [at] python>wrote:
> changeset: 4281:af61fe9a56fb
> user: Eric V. Smith <eric [at] trueblade>
> date: Thu Apr 19 18:56:22 2012 -0400
> Note that ImportError will no longer be raised due to a missing
> __init__.py file.
> pep-0420.txt | 5 +++++
> 1 files changed, 5 insertions(+), 0 deletions(-)
> diff --git a/pep-0420.txt b/pep-0420.txt
> --- a/pep-0420.txt
> +++ b/pep-0420.txt
> @@ -148,6 +148,11 @@
> path. With namespace packages, all entries in the path must be
> +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.
> At PyCon 2012, we had a discussion about namespace packages at which
> PEP 382 and PEP 402 were rejected, to be replaced by this PEP _.
> Repository URL: http://hg.python.org/peps
> Python-checkins mailing list
> Python-checkins [at] python