On Fri, Jun 18, 2010 at 11:47 AM, Mark Ramm <span dir="ltr"><<a href="mailto:mark@geek.net">mark@geek.net</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><div></div><div class="h5">On Thu, Jun 17, 2010 at 5:41 PM, "Martin v. Löwis" <<a href="mailto:martin@v.loewis.de">martin@v.loewis.de</a>> wrote:<br>
>> It does? I thought PyPI kept everything around (but hidden) unless the<br>
>> author went in and manually deleted old stuff. You just need to go to a<br>
>> deep link, e.g., <a href="http://pypi.python.org/pypi/SomePackage/0.1" target="_blank">http://pypi.python.org/pypi/SomePackage/0.1</a><br>
><br>
> Sure, but owners *do* manually delete old stuff.<br>
<br>
</div></div>Am I wrong in remembering that old packages get dropped from the<br>
simple index?<br>
<br>
I'm not saying they get deleted from the server, but they are made<br>
unavailable to easy_install without special knowledge of how to get<br>
them, So old packages can have requirements in setup.py which become<br>
unavailable for simple install.<br></blockquote></div><br>If you give pip or easy_install (or I assume buildout) a requirement like Foo==0.1, then they will look at <a href="http://pypi.python.org/simple/Foo/0.1">http://pypi.python.org/simple/Foo/0.1</a>, and if the release is hidden that will still return the links for that version of the package. If you give a version like Foo<=0.1 then it won't work (assuming 0.1 is hidden), as there's no deep link that either installer will look at.<br>
<br>A weird case is that links in long_description in old releases will show up regardless, so if you actually want to purge a link (e.g., to a non-existent repository) then it require editing all versions of the package. This might be unintentional.<br clear="all">
<br>-- <br>Ian Bicking | <a href="http://blog.ianbicking.org">http://blog.ianbicking.org</a><br>