On Tue, May 12, 2009 at 3:45 PM, Iain Duncan <[email protected]> wrote: > > On Tue, 2009-05-12 at 18:40 +0200, Antonio Beamud Montero wrote: >> >> How do you name virtual environments? >> And where do you store this enviroments? >> Exists any recipe to manage several virtual envs and not die trying it? :) >> > > I came up with a slightly odd configuration that I really like, but Ian > said it should work fine. I make my build script turn the top level of a > project checkout *into* the virtual env, following a project layout I > cobbled together from combinations of "Foundations of Agile Python > Development" and "Continuous Integration". > > So a full build checks out the whole project, including source for all > third party dependencies, wipes the old virtual env, creates a fresh one > in the current dir, installs the dependencies, and then builds and > installs the project. Nothing needs to come from the net, the only local > variable is the python install, and the build is 100% new and repeatable > aside from the base python.
But the virtualenv contains symlinks to the system Python libraries. How can those be replicated in another location? Or does it assume the system Python has all the same paths as when the virtualenv was created? -- Mike Orr <[email protected]> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
