[13:41:08] <kklimonda> hmm... buildout 2.0 doesn't support include-site-packages and co. has it been deprecated in the meantime, and if so is the "correct" way of creating an isolated python env using a virtualenv?
[13:42:12] <schmir> kklimonda: you can use virtualenv
[13:44:06] <mgedmin> I started using a ~/bin/virtual-bootstrap like this: http://dpaste.de/Hu7ni/
[13:44:14] <mgedmin> because I almost always want an isolated buildout
[13:48:42] <schmir> I use dedicated virtualenv installed by root, with --no-setuptools --no-pip
[13:49:38] <mgedmin> that's... a very good idea actually
[13:49:47] <mgedmin> (a single shared empty read-only virtualenv)
[13:51:51] <J1m> mgedmin, that's why I never understood the desire to have buildout's bootstrap create a virtualenv.
[13:52:50] <mgedmin> well, it's a logical extension of a few ideas: having things Just Work Out Of The Box, combined with the idea of never modifying anything outside the current working directory
[13:52:58] <schmir> J1m: while I'm here, buildout 2 script support doesn't work with scripts that contain "from __future__ import" statements...