How do you host your own egg repository?

Question

Say you\'re on a team that\'s maintaining a lot of internal python libraries(eggs), and for whatever reason uploading them to pypi is not an option. How could you host the l

Answer 1

First of all: If the packages are generic packages should be available publicly, not uploading the packages to PyPI is generally a bad idea, as easy_installing a package that depends on your package means your egg server needs to be up and running, as well as PyPI. For every server involved you get more single-point of failures.

But if it's private packages that should not even be listed on PyPI, or packages only useful as a part of a large system, like Plone, it's another matter. Then you want easy___install and buildout etc's to look for eggs on your server. Doing that is quite straighforward. You just put the eggs directory on a webserver and point to that directory with the -f parameter to easy_install.

Here is an example of such a repository: http://dist.plone.org/release/3.3.1/