Cliff Wells wrote: > On Wed, 2007-08-15 at 19:15 +0200, Neil Blakey-Milner wrote: > >> Or, even better, use virtual-python or workingenv, and never install >> moving targets into your core Python library location. > > Out of curiosity, what does workingenv offer over the standard > setuptools way of doing things? > > http://peak.telecommunity.com/DevCenter/EasyInstall#administrator-installation
It's a lot closer to virtual-python. It works on Windows, unlike virtual-python; though frankly workingenv can be a bit fragile, mostly due to the monkeypatches of Setuptools. I've tried to figure out a way to avoid those monkeypatches, but I've had a hard time. You can also have multiple independent workingenvs easily; it's not user-specific. We run a workingenv for every independent service, with no shared packages (that is, as long as two applications are already going to run in separate processes, we don't share libraries between them). It's easy to make scratch environments as well. workingenv also has some bootstrapping abilities, for setting up complete environments with a single command or updating environments. -- Ian Bicking : [EMAIL PROTECTED] : http://blog.ianbicking.org : Write code, do good : http://topp.openplans.org/careers --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
