[Product-Developers] ANN: plone-devstart (please help test)

David Glick (GW) davidglick at groundwire.org
Mon Mar 12 22:27:41 UTC 2012

On Mar 12, 2012, at 3:05 PM, Martin Aspeli wrote:

On 12 March 2012 21:56, Héctor Velarde <hector.velarde at gmail.com<mailto:hector.velarde at gmail.com>> wrote:
On 12/03/12 17:40, Martin Aspeli wrote:
Buildout does in version 1.5.2. That is not the version Plone 4.1.4 (see

HV> amazing!

If and when we have a reliable way to do this with standard Plone
versions, let's do it. I'd strongly welcome a PLIP to upgrade Plone's
buildout version, but until that's commonplace, we need this type of

HV> are there any risks involved on this, or is just to include zc.buildout = 1.5.2 in Plone's KGS to override the one in ztk?

this can be accomplished easily :-)

Agreed. Thought not for existing/legacy versions of Plone of course.

I don't know if there are risks/problems. I guess it needs a PLIP champion and some testing. Probably still an option for 4.3, less sure about 4.2.

We do need to proceed cautiously.

The mechanism by which zc.buildout 1.5.x isolates itself is by passing -S to the Python interpreter, which makes Python not load site.py.

That means that upgrading to zc.buildout 1.5.x will break installations that used both a virtualenv and a buildout, and installed some eggs into the virtualenv. (Because a customized site.py is how virtualenv sets up a sys.path which includes the virtualenv's site-packages dir.)

I think it will also interfere with installations that are using sitecustomize.py, such as to change the default encoding.


David Glick
Web Developer
davidglick at groundwire.org


The NPO Engagement Party 2012.<http://www.npoengagementparty.com> So much more fun than the wedding reception.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.plone.org/pipermail/plone-product-developers/attachments/20120312/e856b423/attachment.html>

More information about the Product-Developers mailing list