plone.recipe.zope2instance needs support for system Python feature of buildout > 1.5
Bug #683584 reported by
Jeff Rush
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
collective.buildout |
Fix Released
|
Undecided
|
Hanno Schlichting |
Bug Description
zc.buildout 1.5 added support for using system Python interpreters for buildouts instead of requiring the use of virtualenv sandboxes. A handful of lines needs to be added to this recipe to support it. The feature makes use of buildout with this recipe much simpler.
To read about this feature in zc.buildout:
http://
I am attaching a patch that adds support to plone.recipe.
Changed in collective.buildout: | |
assignee: | nobody → Hanno Schlichting (hannosch) |
status: | New → Fix Committed |
Changed in collective.buildout: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
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