Why does zope.tales explicitly pin versions in buildout.cfg?
Hello, this is the buildout.cfg in zope.tales: [buildout] develop = . parts = test versions = versions [test] recipe = zc.recipe.testrunner eggs = zope.tales [versions] zope.traversing = 3.4.0 zope.app.publisher = 3.4. Is there a specific reason for having the version pinning? Automatic testing of zope.tales obviously fails using the KGS, because zope.traversing there is 3.7.1. Is it possible to remove the "versions" stanza? Thanks, Fabio
Fabio Tranchitella wrote:
Is there a specific reason for having the version pinning? Automatic testing of zope.tales obviously fails using the KGS, because zope.traversing there is 3.7.1.
Is it possible to remove the "versions" stanza?
Sure. Pinned versions are OK for a maintenance branch, but not the trunk. Shane
* 2009-08-06 08:27, Shane Hathaway wrote:
Sure. Pinned versions are OK for a maintenance branch, but not the trunk.
Thanks, I just committed the change. -- Fabio Tranchitella http://www.kobold.it Free Software Developer and Consultant http://www.tranchitella.it _____________________________________________________________________ 1024D/7F961564, fpr 5465 6E69 E559 6466 BF3D 9F01 2BF8 EE2B 7F96 1564
Shane Hathaway wrote:
Fabio Tranchitella wrote:
Is there a specific reason for having the version pinning? Automatic testing of zope.tales obviously fails using the KGS, because zope.traversing there is 3.7.1.
Is it possible to remove the "versions" stanza?
Sure. Pinned versions are OK for a maintenance branch, but not the trunk.
+1, at least for most libraries. It can get messy not to pin if you depend on a lot of libraries, and frameworks do that. So Grok will continue pinning down versions in its trunk for the time being. :) Regards, Martijn
participants (3)
-
Fabio Tranchitella -
Martijn Faassen -
Shane Hathaway