james: i love you. (sorry *g*)

before pylons i used cgitb a million times for debugging, so i was
really surprised by the simplicity of a possible solution to my problem
when reading your message. well... i put cgitb into my startup.py ->
Server error. No traceback, just the old message. GNAAAAH.

i decided to start completely from begin. pylons 0.9.2, fresh
installation of a pylons app with just one controller that returns
hello world. test with CGIHandler from wsgiref: same result *sigh*.
then i read your message again. flup... okay, let's give flup another
try. i put an additional line into my dispatch.cgi to let flup fallback
to cgi:

os.environ['FCGI_FORCE_CGI'] = 'Y'

and.... tadaaaaa: error with traceback: middleware... multi process...
have read that before... set debug to false... IT WORKS!

tested again with wsgiref and without flup... IT WORKS!

my problem now: the pylons installation on this machine was intended
for development and debugging. it is a remote machine but a secure one
and i am used to vi as editor. now please do not tell me that debugging
without paster serve is impossible... i've got only access through
http_s_...

axel


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/pylons-discuss
-~----------~----~----~----~------~----~------~--~---

Reply via email to