Ian Bicking: the old part of his blog

Re: workingenv.py update

I have to say I've been using workingenv for a while now and it is really helpful. Everyday I need to work with more than one module from subversion and this is a nice way to go. I was having a little bit of trouble getting 2.4 and 2.5 environs going side by side (I think the local easy_install script was getting overwritten) but maybe it was fixed when I blew away my env and started over, can't recall. I'll let you know if it comes up again.

Is there a way to repair an existing workingenv? I know you have been tweaking issues for compatibility w/ setuptools here and there (invalid site.py error, etc). Obviously I haven't looked at the new --confirm option. Maybe that does it.

One thing I'm trying to find time for in my company is convert our hand-rolled continuous integration package to buildbot. I think workingenv would be a nice way to automate the buildbot environment for each test suite. Has anyone tried something like this yet?

Comment on workingenv.py update
by Kumar McMillan

Comments:

Is there a way to repair an existing workingenv? I know you have been tweaking issues for compatibility w/ setuptools here and there (invalid site.py error, etc). Obviously I haven't looked at the new --confirm option. Maybe that does it.

The new version saves your configuration information in .workingenv/*, so you can simply re-run python workingenv.py existing-env. It'll ask you before overwriting any files.

One thing I'm trying to find time for in my company is convert our hand-rolled continuous integration package to buildbot. I think workingenv would be a nice way to automate the buildbot environment for each test suite. Has anyone tried something like this yet?

I haven't, but it definitely seems like a good way to do this.

# Ian Bicking