<br><br><div><span class="gmail_quote">On 4/27/06, <b class="gmail_sendername">Thomas Wouters</b> <<a href="mailto:thomas@python.org">thomas@python.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style="direction: ltr;"><br><br><div></div><div style="direction: ltr;"><span class="q"><span class="gmail_quote">On 4/27/06, <b class="gmail_sendername">Gustavo Carneiro</b> <<a href="mailto:gjcarneiro@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
gjcarneiro@gmail.com</a>> wrote:</span><br></span></div><div style="direction: ltr;"><span class="q"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style="direction: ltr;"><div style="direction: ltr;"><span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div> Besides, Guido's original proposal is not a fix for your problem, either; he only proposes to change the requirement for *sub*packages.
<br></div></blockquote></span></div><div style="direction: ltr;"></div><br> It *is* a solution for my problem. I don't need the __init__.py file for anything, since I don't need anything defined in the the 'foo' namespace, only the subpackages
foo.bar and foo.zbr
.</div></blockquote></span></div><div style="direction: ltr;"><div><br>... No. Guido's original proposal is not a fix for your problem, because *it doesn't affect the 'foo' namespace*. Guido's original proposal still requires foo/__init__.py for your namespace to work, it just makes foo/bar/__init__.py and foo/zbr/__init__.py optional.
</div></div></div></blockquote><div><br> Damn, you're right, I confused subpackage with submodule :P<br> <br> In that case, can I counter-propose to stop requiring the __init__.py file in [foo/__init__.py, foo/bar.py] ? ;-)
<br><br> The proposal would mean that a directory 'foo' with a single file bar.py would make the module 'foo.bar' available if the parent directory of 'foo' is in sys.path.<br><br>/me faces the pitchforks.<br></div></div>
<br>