[mod_python] This is just friggin' weird...

Greetings!

I know that this is but faint help, but if psp.redirect is throwing an
error, who is (eventually) catching it? 

I had a problem once that was somewhat vaguely similar: if the application
tosses an error that none of the application's error handlers can trap and
correct, it 'percolates' its way up to the interpreter's default exception
handlers - and those try to write to sys.stderr (it says here in the Python
manual).

When the PythonDebug directive is set to "On," the error messages are
redirected to the requesting client.  When it's "Off," I have no idea where
they go (/dev/null for all I know...)

So mebbe turn Python Debug On and see what you get?

Best Regards,
Lee E. Brown
(administrator at leebrown.org)

-----Original Message-----
From: mod_python-bounces at modpython.org
[mailto:mod_python-bounces at modpython.org] On Behalf Of Joshua Ginsberg
Sent: Thursday, June 23, 2005 6:09 PM
To: Joshua Ginsberg
Cc: mod_python at modpython.org
Subject: Re: [mod_python] This is just friggin' weird...

Okay, and something else I've discovered... it appears to be hanging on
psp.redirect...

Now, at least in my experience, psp.redirect will throw an error if data has
been written back out to the client when redirect() is called. 
It's not doing that. It's just... hanging.

The way I discovered this was by accident. I was testing it by telnetting to
port 80 and manually entering for data. I accidentally left off a field, and
it hung at a different place it had ever hung before. At that spot, there's
a psp.redirect to an error handler...

So... why? I don't get it.

-jag