On Tue, Jan 22, 2013 at 9:11 AM, Reinout van Rees <[email protected]> wrote: > On 22-01-13 13:55, Jim Fulton wrote: >> >> Use zc.recipe.testrunner 1.3.0. I plan to release a >> zc.recipe.testrunner 2 that is just a copy of 1.3.0.:) > > > Yes, that fixes it. > > Now I see a different problem: > > File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2475, in > scan_list > raise ValueError("Expected "+item_name+" in",line,"at",line[p:]) > ValueError: ('Expected version spec in', 'zc.buildout[] ==>=2.0.0b1', 'at', > ' ==>=2.0.0b1') > > > I boils down to buildout injecting minimum requirements for buildout and > zc.recipe.egg in the version part like ">=2.0.0b1" > > Apparently this is new?
Yup > buildout-versions expects only "real" versions in > there, so it adds an "==", which results in a weird-looking fat arrow: > "==>=2.0.0b1". > > I think I can compensate for that. > > > But... is it true that you can put ">=" requirements in the versions list? Yes: http://pypi.python.org/pypi/zc.buildout/2.0.0b1#a5-2012-12-01 http://pypi.python.org/pypi/zc.buildout/1.7.0#id9 This isn't expected to be a widely used feature. It's used by buildout 2 to keep itself from downgrading itself to a final release. It's used by buildout 1 to keep itself and some recipes from upgrading to 2. I'm surprised buildout 1.7.0 didn't break buildout-versions. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton Jerky is better than bacon! http://zo.pe/Kqm _______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
