Jim Fulton

It seems to me that the easiest fix is to check to see if the setuptools (or buildout) distributions are outside the buildout eggs directory. Of course, now that there...

FTR I said: "I can't reproduce this with buildout 2.6.0 or 2.5.3 for the case when the buildout and virtualenv directories are different, because buildout won't upgrade if it's not...

Another idea (170410.1) When doing a local bootstrap, make sure that buildout and it's dependencies are installed in the eggs directory. This means we may have to download buildout, setuptools,...

You can package buildouts in a number of ways, but not as Python packages. To make source tarballs, we used to use: https://pypi.python.org/pypi/zc.sourcerelease You can then use these to created...

I think I just realized what's causing this. This is a bug I introduced in 2.3 and I think I know how to fix it. (It makes me sad that...

Some high-level comments. 1. Buildout really needs an API that it can use. Given the convergence of the rest of the Python community on pip, I'd prefer in the long...

Someone I respect recently suggested to me that buildout should be more language neutral, and that assembling a Python script should be the responsibility of a recipe with very little...

It looks like buildout isn't including appdirs in it's environment for some reason.

This is weird. I deleted the old appdirs egg, has to re-bootstrap my shared buildout and now it works fine. :/ I've succeeded flailtastically like this before, until...

See https://github.com/buildout/buildout/issues/382 and https://github.com/benjaminp/six/issues/188 At a minimum we should catch this error and display the directory. Perhaps we should even detect the version mismatch.