Comment 1 for bug 242370

Revision history for this message
Maurits van Rees (maurits-vanrees) wrote : Re: grokproject should pin versions in setup.py

I pinned the grok version in the generated setup.py; committed in r87875.

As for the zc.buildout dependency of grokproject itself: in my own (Plone) buildouts I never pin zc.buildout or setuptools in the version.cfg as a bootstrap will always get the newest versions of those two and will then give a conflict error when running bin/buildout after that. So I am inclined to not pin those in the setup.py of grokproject or a generated project either.

As for PasteScript: when I change the dependency from "PasteScript>=1.6" to "PasteScript==1.6.3" I get this error when running bin/buildout in my grokproject checkout:

===================================
While:
  Installing grokproject.
Error: There is a version conflict.
We already have: PasteScript 1.6.2
but grokproject 0.8dev requires 'PasteScript==1.6.3'.
===================================

Ah, but of course when running "bin/buildout -nv" it gets the new requirement. So that should be fine; committed in r87877.