It's actually an ImportWarning, not Error (or at least that's what I meant on import-sig). If the module is eventually found then there is no error.<br><br><div class="gmail_quote">On Thu, Apr 19, 2012 at 18:56, eric.smith <span dir="ltr"><<a href="mailto:python-checkins@python.org">python-checkins@python.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><a href="http://hg.python.org/peps/rev/af61fe9a56fb" target="_blank">http://hg.python.org/peps/rev/af61fe9a56fb</a><br>
changeset: 4281:af61fe9a56fb<br>
user: Eric V. Smith <<a href="mailto:eric@trueblade.com">eric@trueblade.com</a>><br>
date: Thu Apr 19 18:56:22 2012 -0400<br>
summary:<br>
Note that ImportError will no longer be raised due to a missing __init__.py file.<br>
<br>
files:<br>
pep-0420.txt | 5 +++++<br>
1 files changed, 5 insertions(+), 0 deletions(-)<br>
<br>
<br>
diff --git a/pep-0420.txt b/pep-0420.txt<br>
--- a/pep-0420.txt<br>
+++ b/pep-0420.txt<br>
@@ -148,6 +148,11 @@<br>
path. With namespace packages, all entries in the path must be<br>
scanned.<br>
<br>
+Note that an ImportError will no longer be raised for a directory<br>
+lacking an ``__init__.py`` file. Such a directory will now be imported<br>
+as a namespace package, whereas in prior Python versions an<br>
+ImportError would be raised.<br>
+<br>
At PyCon 2012, we had a discussion about namespace packages at which<br>
PEP 382 and PEP 402 were rejected, to be replaced by this PEP [1]_.<br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
--<br>
Repository URL: <a href="http://hg.python.org/peps" target="_blank">http://hg.python.org/peps</a><br>
</font></span><br>_______________________________________________<br>
Python-checkins mailing list<br>
<a href="mailto:Python-checkins@python.org">Python-checkins@python.org</a><br>
<a href="http://mail.python.org/mailman/listinfo/python-checkins" target="_blank">http://mail.python.org/mailman/listinfo/python-checkins</a><br>
<br></blockquote></div><br>