The server always sets wsgi.multiprocess, but in the dev environment the processes aren't recycled that often so it's actually almost always okay (no worse than using it with paster --reload), but evalerror still disables itself.
On Wed, May 6, 2009 at 1:35 PM, Mike Orr <[email protected]> wrote: > > On Wed, May 6, 2009 at 9:50 AM, Ben Bangert <[email protected]> wrote: > > On May 6, 2009, at 12:54 AM, Wichert Akkerman wrote: > > > >> I click on the + and get a javascript error. > > > > What type of environment? What wsgi server? I can see why it wouldn't > work > > under GAE, since there's no guarantee you'll get back to the same process > > (it relies on a *single* long-lived process to ask for more debug info). > > The GAE problem also occurs in the development server. You get a > cgitb traceback instead of the interactive traceback. Ian thinks > WebError is disabling itself due to something in the environment, > which may be related to David Wilson's workaround. > > Wichert's problem sounds completely different, and is not something > I've encountered. I'm also curious what the Javascript error is. If > it is a case of the server being restarted or a different server > reached, the message would say that. Something like "/_debug/123ABC > is invalid (was the server restarted?)". > > -- > Mike Orr <[email protected]> > > > > -- Ian Bicking | http://blog.ianbicking.org --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
