a bootstrap option to create a virtualenv
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Buildout |
New
|
Undecided
|
Unassigned | ||
Bug Description
Buildout 2 has removed the "noble effort" to isolate buildout from site-packages to avoid complexity. I agree with the complexity, but now I find myself writing a long email to explaining how to create a virtualenv.
What about an option to bootstrap, say -i for isolate, that can create a virtualenv for that buildout? The bootstrap procedure can then automatically download virtualenv, create an environment and make sure that 'bin/buildout' uses that virtualenv's python.
Where should this environment be installed? I'm not entirely sure - parts/ve would be one option, but that's too early I think - only buildout fills up parts and should be able to work with an empty parts. <projectdir>/ve/ would be another option, or even <projectdir>/.ve/. I think a virtual 've' directory wouldn't hurt.
