On 03-11-14 11:28, Reinout van Rees wrote:
I'm on to something.
https://github.com/buildout/buildout/pull/201
Multiple complications at the same time. The new buildout was stricter
than the old one with constraining dependencies to the right version.
For instance when installing dependencies for extensions.
mr.developer depends on buildout and setuptools.
Constraining them to the right version fails if the buildout was
bootstrapped with a different buildout/setuptools version...
Extra complication was that installing extensions happens BEFORE
checking if setuptools/buildout needs upgrading/downgrading :-)
The pull request also solves a problem with recipes that themselves have
dependencies.
pdp.recipe.noserunner depends on nose, which can be installed globally.
If that's the wrong version, you get an unclear version conflict.
With the pull request, buildout will ignore that conflict and instead
will forcefully install the right version. This only happens when
installing buildout/setuptools/extensions/recipes, though, not with the
regular install/dependency handling.
Reinout
--
Reinout van Rees http://reinout.vanrees.org/
[email protected] http://www.nelen-schuurmans.nl/
"Learning history by destroying artifacts is a time-honored atrocity"
_______________________________________________
Distutils-SIG maillist - [email protected]
https://mail.python.org/mailman/listinfo/distutils-sig
