workingenv.py + Aspen = BLAM!!!!1

So I finally got around to trying out workingenv.py, which took all of about 2 minutes. It's wonderful beyond my wildest expectations!

Aspen websites all have a "magic directory" named __ (that's two underscores), which is a Unix-style userland for all the junk needed to run your website. Sweep all the crap under that rug, and you can use the site root itself to store actual hierarchical data and things.

The bottom line is that workingenv dovetails perfectly with this scheme. Make the magic directory your workingenv, and wherever you are you can install and access the libraries for the site you're currently working on. What a boon! Thanks Ian!

PS: For the NIH record, I didn't invent workingenv. Am I cured yet?

Update: Since all magic directories are named __, workingenv's new prompt isn't that helpful. To make it more so, apply this patch. Feed back to Chad Whitacre.