Here's some not-quite-ready feedback from the last couple of days:

-- the session.py code won't work on Windows w/o some tweaking -- the
time module on windows doesn't have strptime.  See

http://www.ocf.berkeley.edu/~bac/Askewed_Thoughts/code/Python/Scripts/strptime.p
y

for a pure-Python implementation.

-- The method used in expire_cookie didn't work for me in some
browsers.  I need to repro, though.

-- If I have a syntax error in my Python code, the Apache log complains
of being unable to modify the .ptlc file -- I need to erase the .ptlc
file, reload to get the relevant traceback.  I haven't dug to find out
the cause.

-- My request for Quixote's evolution is a little more built-in tools
that make some things easier, like examples for how to persist the
SessionManager, dealing w/ users & logins etc.  Something like a
"standard library" of tricks which encapsulate knowledge that seasones
web developers know that the rest of us don't.

-- I still feel like there's some "magic" between the .cgi program and
the app itself which puzzles me.  If I want to persist sessions, I must
add the persistence at the level of the 'stub' .cgi program, but I'm a
little puzzled w.r.t. the import/namespace issues around how those two
interact.  I should probably read the code, but whatever =).  This
comment emerges from some weird problems I'm having trying to persist
data w/ ZODB, and is probably the result of ZODB-confusion more than
Quixote confusion.

-- More generally, the biggest problem I have with Quixote is that that
I have with all web dev't -- the compile/run/edit cycle is lengthened
too much by the need to work with the browser (forget cookies, etc.).  I
think some adjunct tools that helped with  that would increase
productivity a lot.  Not sure what that means yet =).  I suppose what I
really want is a deeply scriptable browser.

--david