Martin Aspeli wrote:
Ian Bicking wrote:
If you use the easy_install script in the workingenv bin/, then you
don't have to activate the environment. Very similar to buildout,
workingenv scripts contain their path/environment.
Right, thanks for pointing that out.
I should also mention that,
Daniel Nouri wrote:
[...]
- There is a single file that shows me what eggs and development eggs
make up my package. This makes it easy to add new eggs, for example -
and also easy to remove them again. With workingenv-based solutions, you
can specify a file full of eggs to install when it's
Ian Bicking wrote:
One of the things that I think is pretty easy with workingenv, and a bit
confusing with buildout, is moving one package into development. In
workingenv you get the package you want (however you do that -- check
out a branch, make your own local repository, unpack a
