Re: [Zope-dev] Why does zope.tales explicitly pin versions in buildout.cfg?

2009-08-06 Thread Fabio Tranchitella
* 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

Re: [Zope-dev] Why does zope.tales explicitly pin versions in buildout.cfg?

2009-08-06 Thread Martijn Faassen
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

[Zope-dev] Why does zope.tales explicitly pin versions in buildout.cfg?

2009-08-05 Thread Fabio Tranchitella
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

Re: [Zope-dev] Why does zope.tales explicitly pin versions in buildout.cfg?

2009-08-05 Thread Shane Hathaway
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,