On Apr 20, 3:30 pm, Ian Bicking [EMAIL PROTECTED] wrote:
Chas Emerick wrote:
For various reasons, I need to be able to bring up and tear down
Pylons apps from an already-running Python process. I took a look at
what pastescript does in the background when one executes a `paster
serve
suppose I'll just hook into start_response
directly.
Thanks,
Chas Emerick
Snowtide Informatics
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
pylons-discuss group.
To post to this group, send email to pylons-discuss
to get around this? I've gotten too used to the
fantastic interactive stack traces, etc. If no workaround is readily
available, I'll just hook into start_response directly.
Thanks,
Chas Emerick
Snowtide Informatics
--~--~-~--~~~---~--~~
You received this message
file option so as to not disturb expectations elsewhere (or, even
better, add an attribute to the Response object so that each action
could determine the appropriate behaviour, rather than having the
setting apply application-wide).
Chas Emerick
Snowtide Informatics
rendering costs)
So, thanks again to everyone who helped us get these sites off the
ground, and looking great!
Chas Emerick
[EMAIL PROTECTED]
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
pylons-discuss group.
To post
that any
and all headers going into a Response are (a) removed if their value is
None, and (b) flattened using str() otherwise.
Chas Emerick
[EMAIL PROTECTED]
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
pylons
OK, my bad. This problem was entirely my fault, so I figured I should
at the very least let everyone know. :-)
The issue was in our lighttpd config. This line was catching the 404's
(the remains of a RoR fcgi config):
server.error-handler-404 = /
What I still don't understand is why 404's
We just updated to 0.9 final, and started seeing these errors -- we saw
both varieties of error (one under flup_scgi_thread, the other under
PasteScript#wsgiutils.
Installing the latest beaker from the trunk as Philip suggested did the
trick.
Just thought I'd confirm Mike's success.
Chas
Hi all. We're moving into heavy testing for our new website and a few
accompanying apps (all based on pylons/sqlobject/kid), but we've run
into a serious problem with leaking database connections.
Briefly put, if we use a
sqlobject.postgres.pgconnection.PostgresConnection as the _connection
