Hi Jeff,
Thanks for the patch!
But I don't fully understand this. Why would I want to use a system Python instead of a virtualenv? It seems to me zc.buildout should be trying to provide a similar isolation as is provided by virtualenv, to "save" people from having to do:
$ virtualenv --no-site-packages foo ; cd foo ; bin/pip install zc.buildout ; bin/buildout init
In other words, create a buildout inside a virtualenv to isolate from site-packages. Does this patch provide such isolation? And if so, how?
Thanks for any comments,
Alex
Hi Jeff,
Thanks for the patch!
But I don't fully understand this. Why would I want to use a system Python instead of a virtualenv? It seems to me zc.buildout should be trying to provide a similar isolation as is provided by virtualenv, to "save" people from having to do:
$ virtualenv --no-site-packages foo ; cd foo ; bin/pip install zc.buildout ; bin/buildout init
In other words, create a buildout inside a virtualenv to isolate from site-packages. Does this patch provide such isolation? And if so, how?
Thanks for any comments,
Alex