I just wanted to announce the release of collective.eggproxy (http://pypi.python.org/pypi/collective.eggproxy/0.2.0)
collective.eggproxy is a smart mirror for PyPI, thaught and coded by my colleague Bertrand Mathieu.
It will collect packages on PyPI only when a program like easy_install or zc.buildout asks for it. In other words, unlike some mirrors that act like rsync and get the whole PyPI base (more than 5 gigas) collective.eggproxy will only get what you need.
At first run collective.eggproxy downloads pypi index and builds a page of links. When a software asks for a specific package, version, etc. collective.eggproxy downloads it if needed and stores it locally.
Want to give a try ? try it in two lines with easy_install:
easy_install collective.eggproxy eggproxy_run
That’s it !
Cool.
Here’s a related question:
I want to set up an internal PyPI repository, so our users can type “easy_install PACKAGE”, and not care if PACKAGE was something we built internally, or a publicly available package.
Does such a thing exist?
Comment by Alec Munro — September 24, 2008 @ 4:42 pm |
@Alec: easy_install has to work with a index server. If you have an internal PyPI repository, as long as it contains all package you can use -i to point to it. If you have packages spread to several PyPi repositories, you can’t at this point.
A patch was proposed in setuptools project so it can deal with several indexes, but it has not been reviewed yet.
Although the Distribute fork I am launching will probably add this feature next month.
Comment by Tarek Ziadé — September 24, 2008 @ 7:49 pm |
Nice… just giving this a whirl.
A few notes, eggproxy_run appears to be looking for a /var/www/ directory. In the absence of such a directory I got an error.
Of course the /var/www/ directory will need to have permissions suitable for “eggproxy_run” to write stuf to it.
Comment by David Bain — December 15, 2008 @ 7:15 pm |