On Jul 6, 5:56 pm, "Mike Orr" <[EMAIL PROTECTED]> wrote: > So then we just need a reminder in the deployment options chapter.
Yeah. I see the problem as this: 1- Pylons offers some great features to aid in debugging. 2- These features are necessary and make sense for being enabled at start for the dev environment 3- They must be turned off for depoloyment 4- Most people will not read the docs straight through. What developers do? They play or play + skim! Personally, my ideal solution would be this: 1- add an 'allow_trackback_shell' debug option in the conf, have debug enabled by default - but that option disabled 2- alter pylons.error.error_template to mention that - - a - the trackback shell can be enabled/disabled - - b - that this error page can be turned off by setting debug to false It's really just about making answers apparent to developers where they're going to look for them. I can imagine no better place than staring directly at them. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
