Hi, What you are describing seems a lot like the task/way of operation of Buildout. http://pypi.python.org/pypi/zc.buildout Perhaps you should take a look at it as it's mode of operation is to maintain a collection of "eggs" either from sources or repos.
Personally I like the virtualenv approach (using pip and a requirements.txt file) more but in the few projects i have used buildout it's fine. As for your other question. Yes if setup.py has changed then you must make python/distutils be aware of it. That's the only occasion where you must rerun it, at least that I know of. On Wed, Nov 2, 2011 at 5:33 AM, Andrea Crotti <andrea.crott...@gmail.com> wrote: > Supposing that we have a directory with many eggs that compose our > framework. > > All these eggs might (or might not be) used by applications that we write. > So at the moment we run "python setup.py develop" on all of them. > > To avoid to waste too much time, however, the builder does a make-like > operation, checking if "setup.py" was modified. > > So since I'm rewriting a new system to build/develop: > - does it make sense to re-run develop when setup.py changes. > And if yes are there other possible conditions which would force me to > re-run it? > > - what could be a good way to implement a similar mechanism? > Is there anything already I could use? > > I've seen watchdog (http://pypi.python.org/pypi/watchdog) which looks very > interesting, > and might be good to implement a service, but maybe it's overkill... > _______________________________________________ > Distutils-SIG maillist - Distutils-SIG@python.org > http://mail.python.org/mailman/listinfo/distutils-sig > _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig