Showing content from http://mail.python.org/pipermail/python-dev/attachments/20060427/802a20f6/attachment.html below:
<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><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;"><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></div><div style="direction: ltr;"><span></span></div><div style="direction: ltr;"><span class="q"><span class="gmail_quote">On 4/27/06, <b class="gmail_sendername">Phillip J. Eby</b> <
<a href="mailto:pje@telecommunity.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
pje@telecommunity.com</a>> wrote:</span></span></div><div style="direction: ltr;"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"></blockquote>
</div><div style="direction: ltr;"><span class="q">
At 03:48 PM 4/27/2006 +0200, Bernhard Herzog wrote:<br>>"Gustavo Carneiro" <<a href="mailto:gjcarneiro@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">gjcarneiro@gmail.com
</a>> writes:<br>><br>> > Now the problem. Suppose you have the source package python-foo-bar,
<br>> > which installs $pythondir/foo/__init__.py and $pythondir/foo/bar.py. This<br>> > would make a module called "foo.bar" available. Likewise, you can have the<br>> > source package python-foo-zbr, which installs
<br>> $pythondir/foo/__init__.py and<br>> > $pythondir/foo/zbr.py. This would make a module called "foo.zbr"<br>> available.<br>> ><br>> > The two packages above install the file $pythondir/foo/__init__.py. If
<br>> > one of them adds some content to __init__.py, the other one will overwrite<br>> > it. Packaging these two packages for e.g. debian would be extremely<br>> > difficult, because no two .deb packages are allowed to intall the same file.
<br>> <br></span></div><div style="direction: ltr;"><span class="q">>Yet another solution would be to put foo/__init__.py into a third<br>>package, e.g. python-foo, on which both python-foo-bar and
<br>>python-foo-zbr depend.</span></div><div style="direction: ltr;"></div></div></blockquote></div></div><div style="direction: ltr;"><span class="q"><div style="direction: ltr;"><div><br> You can't be serious. One package just to install a __init__.py file?
</div></div></span></div><div style="direction: ltr;"></div><div><br>Sure. Have you counted the number of 'empty' packages in Debian lately?</div></blockquote><div><br> Sure. That is already a problem; let's not make it a worse problem for no good reason; I haven't heard a good reason to keep the __init__.py file besides backward compatibility concerns.
<br> </div><br><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></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
.<br><br>
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