On Sat, Jul 18, 2009 at 12:56 PM, Sridhar Ratnakumar <span dir="ltr"><<a href="mailto:sridharr@activestate.com">sridharr@activestate.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Both easy_install and pip uses similar method to find download URLs for packages. They are not very unreliable - see the new issues in Distribute tracker:<br>
<br>
<a href="http://bitbucket.org/tarek/distribute/issues/?status=new&reported_by=srid" target="_blank">http://bitbucket.org/tarek/distribute/issues/?status=new&reported_by=srid</a><br>
<br>
Hence I suggest that we create a separate project containing just this indexing code .. and let Distribute and pip use it via install_requires. Thoughts?<br>
</blockquote><div><br>pip won't require any installer, or have any dependencies, because that would be too cruel to users. Potentially pip could include code via a build process (what virtualenv does for few things), but the code would have to be small and light. And I'm not sure if the code would be acceptable even then. pip's code for finding packages includes a lot of logging (using pip's logging system) and I wouldn't replace it with something that had less functionality.<br>
</div></div><br>-- <br>Ian Bicking | <a href="http://blog.ianbicking.org">http://blog.ianbicking.org</a> | <a href="http://topplabs.org/civichacker">http://topplabs.org/civichacker</a><br>