On Mon, Aug 30, 2010 at 1:06 PM, Chris Withers <ch...@simplistix.co.uk> wrote: > Gary Poster wrote: >>> >>> It's not like I want my system matplotlib in one part and a locally >>> failing-horribly buildout-installed matplotlib in another part. >> >> No, but single buildouts are used to install different sections with >> entirely different requirements, including different Python versions. > > This feels like needless complexity to me.
This is a requirement we had here at ZC. It wasn't needless. > If a different python is needed, it should be in its own buildout. > If you need to bundle a bunch of buildouts together because of this, use a > recipe that runs "sub buildouts" in a separate process... It's possible that this would be a better approach. It's true that supporting multiple Python interpreters is a pain. I don't have this need atm, so I'm not motivated to try your solution. :) I wonder what other people think. Does anyone else have current need to deal with multiple Python versions in the same buildout? Jim -- Jim Fulton _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
