Ian Bicking: the old part of his blog

Re: Working env comment 000

I think that would be a logical way to do it. I was admittedly surprised that system-wide setuptools was required by working-env, since I was used to putting it locally into a virtual-python. I think it would be less hassle if it were possible to use working-env as a pre-setuptools bootstrap. Perhaps working-env could optionally/automatically run ez_setup.py within the newly-created environment?

I've switched back to virtual-python for now :)

Comment on Working env comment 000
by Matthew Scott


I have to second this comment. The whole reason for me running something like working-env or virtual-python is so that I don't have to mess with my virgin Python installation. If I have to install setuptools first, it kind of defeats the purpose....

# mbogosian