manual eggs downloads?

[Harry George]

"eggs" are wonderful for no-hassle get-all-the-dependencies. However,
they can trigger hands-off downloads from various sites. This is Bad
News for corporate environments in which every download is carefully
pre-approved.

A tarball with a subdirectory of "third_party" packages is ok. A web
page simple listing the third party sites and the recommended
downloads is ok. Automatically downloading is not ok.

Is there some way in the eggs mechanism to just get a list of the
proposed downloads, and let the user take the actions manually?

 

[Jorge Vargas]

"eggs" are wonderful for no-hassle get-all-the-dependencies. However,
they can trigger hands-off downloads from various sites. This is Bad
News for corporate environments in which every download is carefully
pre-approved.

A tarball with a subdirectory of "third_party" packages is ok. A web
page simple listing the third party sites and the recommended
downloads is ok. Automatically downloading is not ok.

Is there some way in the eggs mechanism to just get a list of the
proposed downloads, and let the user take the actions manually?

that is not implemented yet, also you may want to take this to the
distutils-sig list.

what you can do is read the egg's setup.py for it's dependencies, but
this can turn into something like red hat's dep hell.