idea - keeping package index code (in pip, distribute) separate
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: http://bitbucket.org/tarek/distribute/issues/?status=new&reported_by=srid 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? -srid
At 10:56 AM 7/18/2009 -0700, Sridhar Ratnakumar wrote:
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:
http://bitbucket.org/tarek/distribute/issues/?status=new&reported_by=srid
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?
In order for install_requires to work, you need something like easy_install in the first place... and a way to bootstrap it. You could perhaps take setuptools.package_index or something like it, bundle it with pkg_resources, and have a nice little core support for dependency handling, downloading, and local package queries. Then, you could put it in the stdlib... kind of like I proposed in PEP 365. ;-) Alternately, you need a replacement for ez_setup.py that's a stripped-down cross between pkg_resources and setuptools.package_index, or that can at least *download* that combination for you and then run other stuff.
On Sat, Jul 18, 2009 at 12:56 PM, Sridhar Ratnakumar < sridharr@activestate.com> wrote:
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:
http://bitbucket.org/tarek/distribute/issues/?status=new&reported_by=srid
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?
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. -- Ian Bicking | http://blog.ianbicking.org | http://topplabs.org/civichacker
participants (3)
-
Ian Bicking -
P.J. Eby -
Sridhar Ratnakumar