[Grok-dev] grokproject pins setuptools, zc.buildout et.al.

[Maurits van Rees]

Hanno Schlichting, on 2009-11-06:
> On Fri, Nov 6, 2009 at 11:45 AM, Jan-Wijbrand Kolman
><janwijbrand at gmail.com> wrote:
>> I'm ambivalent about this topic: pinning the versions of zc.buildout and
>> setuptools and related packages in the version list of a project.
>
> I think the correct solution to this problem is to release a new
> bugfix release of Grok (grokproject?), which has an updated setuptools
> version in it ;-)
>
> At least in the Plone-world we depend quite heavily on buildout and
> have had several times where changes in buildout broke recipes or
> where newer versions of recipes only work with newer versions of Plone
> itself.
>
> We adopted a strict "pin everything" policy that includes any
> packages, even the build infrastructure. This works pretty well for
> us.

+1

Minimum versions in setup.py is fine, exact versions not.

Pinning exact versions in a buildout config file still allows anyone
to override them when problems like these occur, so that is still fine.

-- 
Maurits van Rees | http://maurits.vanrees.org/
            Work | http://zestsoftware.nl/
"This is your day, don't let them take it away." [Barlow Girl]