-> > First, right now Quixote seems to be fairly closely tied to the CGI
-> > framework, in that it must have at least the PATH_INFO environment
-> > variable (and probably others) defined
->
-> Yes, but you should be able to get away with just defining the 2 or 3
-> environment variables that Quixote relies on.  Read the source to find
-> out which ones they are.  ;-) (Hint: grep for 'environ'.)

Err, thanks ;).  What I was *really* hoping for was a commitment from
you guys to not use additional environment variables in the future!
I'll just do a grep each time you create a new version ;).

-> > Second, something very weird is happening with the Publisher initialization
-> > in PyWX's multithreaded environment.
-> [...]
-> > The first crashes my application with a malloc error,
-> >
-> > =
-> > #0  0x400e91d9 in chunk_alloc (ar_ptr=0x40389074, nb=1075435040)
-> >     at malloc.c:2843
-> > #1  0x400e9028 in __libc_malloc (bytes=348) at malloc.c:2811
-> > #2  0x4024d97e in PyFrame_New (tstate=0x81e3578, code=0x8315b20,
-> >     globals=0x83182f4, locals=0x0) at Objects/frameobject.c:149
-> > ...
-> > =
->
-> Oooh, yuck.  Which version of Python?  If not in (2.1.2, 2.2): upgrade.
-> (Also, which OS?)

Python 2.1.2, Linux.  I'll try it out on 2.2 once I have a clean machine
somewhere to install it on.

Oh, and since I don't hear it enough on the list: you guys have done a great
thing with Quixote.  Very slick & easy to use; I may be in love.

--titus