Interesting that we've just been discussing making a frozen Pylons
release with all its dependencies because something new has just
broken. When I deployed an application to a new server and it raised
an exception, a second exception occurred in WebError and masked the
first one. It may not be in WebError itself but in
distribute/setuptools, because the secondary error was "KeyError:
setuptools". It broke the interactive traceback completely; I just get
the low-level Paste "Internal Server Error" (in teletype font).
So I made a requirements.txt from the slightly-older versions on my
workstation ("pip freeze >requirements.txt"), installed that on the
server ("pip install -r requirements.txt"), and the problem went away.
I'm leaving for PyCon tomorrow morning so I won't be able to follow up
on this until I get back, but I wanted to let people know in case it
happens to you in the meantime.
And maybe somebody who's currently using Pylons can try to reproduce
this. Make a new virtualenv, install an existing Pylons application
into it, and trigger an exception in one of the actions. The specific
exception I had was trying to access a PostgreSQL table that didn't
exist in the reflected metadata (because the table in fact was
missing). But I think it would happen with any exception that would
normally trigger the interactive traceback.
--
Mike Orr <[email protected]>
--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
