[Grok-dev] grokproject pins setuptools, zc.buildout et.al.
roger.erens at e-s-c.biz
Mon Nov 9 19:05:30 EST 2009
On Fri, Nov 6, 2009 at 19:17, Maurits van Rees
<m.van.rees at zestsoftware.nl> wrote:
> Sebastien Douche, on 2009-11-06:
>> On Fri, Nov 6, 2009 at 16:30, Maurits van Rees
>><m.van.rees at zestsoftware.nl> wrote:
>>>> We adopted a strict "pin everything" policy that includes any
>>>> packages, even the build infrastructure. This works pretty well for
>>> Minimum versions in setup.py is fine, exact versions not.
>> It could be great to use buildout to pin minimum versions and let
>> setup.py empty.
> -1. That would just mean you allow a user to pick a version that you
> know is not going to work.
I don't understand; can you elaborate? I mean, someone who can edit
buildout.cfg is also able to edit setup.py. Or isn't that the issue?
More information about the Grok-dev