On 17 February 2002, Titus Brown said:
> 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'.)

> plus, there's some weird fCGI
> interconnection that I haven't looked at.

You shouldn't have to worry about that.  FastCGI is complex and hairy
because it tries to make it really easy to convert plain CGI programs to
FastCGI, ie. you can write FastCGI programs pretty much to the CGI spec.
But if you're using neither CGI nor FastCGI, I don't think that matters
a whit.

> Are there any plans to make
> this tie more explicit, for example by no longer passing in os.environ as
> a whole?

You could just pass in another environ dict with just the keys that
Quixote needs.

> 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?)

        Greg
--
Greg Ward - software developer                gward@mems-exchange.org
MEMS Exchange                            http://www.mems-exchange.org