<div class="gmail_quote">On Fri, May 4, 2012 at 11:13 AM, Eric V. Smith <span dir="ltr"><<a href="mailto:eric@trueblade.com" target="_blank">eric@trueblade.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
3. The zipimport finder currently looks for "path/" to detect if a<br>
'directory' exists and could be a namespace portion. However, this is a<br>
valid zip file:<br>
Archive: namespace_pkgs/missing_directory.zip<br>
Length Date Time Name<br>
--------- ---------- ----- ----<br>
0 2012-05-04 04:45 bar/<br>
35 2012-05-04 04:45 bar/two.py<br>
26 2012-05-04 04:45 foo/one.py<br>
--------- -------<br>
61 3 files<br>
The current code will treat "bar" as a possible portion, but not "foo".<br>
We discussed a number of ways to address this, but I'm unconvinced<br>
they're worth the hassle and runtime expense. But in any event, it's an<br>
issue for another day and doesn't affect the PEP's acceptance one way or<br>
the other.<br></blockquote><div><br>FYI, the zip files produced by distutils do not include the empty directory. Actually, I'm not sure when/where I've ever seen an empty directory listed in a zipfile.<br><br>IMO, the no-explicit-directory case should be handled, if for no other reason than that it shouldn't randomly break depending on which archiving tool you used to create the zipfile with. <br>
</div><br></div>