[Zope-dev] zc.buildout "not upgrading" issue (was Re: RFC: 3.4.1 KGS?)

Marius Gedminas marius at gedmin.as
Fri Apr 2 09:02:53 EDT 2010


A: Because it makes the logic of the discussion difficult to follow.
Q: Why shouldn't I top post?
A: No.
Q: Should I top post?

On Fri, Apr 02, 2010 at 12:29:48PM +0200, Adam GROSZER wrote:
> Hello Wichert,
> 
> Because of our toolchain to release and deploy apps: mypypi and
> keas.build. In fact, because of keas.build depends on zc.buildout.
> 
> Friday, April 2, 2010, 10:53:26 AM, you wrote:
> 
> WA> On 4/2/10 10:36 , Adam GROSZER wrote:
> >> zc.buildout is a tough decision, because it's "not upgrading" issue.
> >> See http://mail.python.org/pipermail/distutils-sig/2010-March/015794.html
> 
> WA> Why would you ever install zc.buildout systemwide? Just as with 
> WA> setuptools I consider that to be a recipe for problems.

Why not do

  python2.x bootstrap.py

and then use

  bin/buildout

instead of the globally-installed buildout?

Marius Gedminas
-- 
http://pov.lt/ -- Zope 3 consulting and development
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
Url : http://mail.zope.org/pipermail/zope-dev/attachments/20100402/6c78dc80/attachment-0001.bin 


More information about the Zope-Dev mailing list