[Grok-dev] Re: grokproject: version pinning in setup.py

[Maurits van Rees]

Philipp von Weitershausen, on 2008-07-01:
> Maurits van Rees wrote:
>> The reasoning would be similar to the reasoning of pinning down the
>> versions of zope packages in the KGS and the version.cfg of grok
>> itself: a newer version of some package may break your project.
>> 
>> For PasteScript I do not expect big changes so keeping the dependency
>> to just a minimum version *should* be fine; but there is no guarantee.
>
> Certainly there's a risk, but unlike with the various Zope packages, we 
> haven't actually experienced problems. Also, the number of dependencies 
> that grokproject has is an order of magnitude smaller than Grok's.

In r87937 I reverted to a PasteScript>=1.6 again.

Also, in r87936 I removed the dependency on zc.buildout as we already
use bootstrap.py-like code to install it on the fly if it is not there
yet.

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