On Fri, 2009-03-06 at 18:12 -0500, Jacob Kaplan-Moss wrote: > On Fri, Mar 6, 2009 at 5:56 PM, Graham Dumpleton > <graham.dumple...@gmail.com> wrote: > > Anyway, the issue is that at the moment mod_wsgi doesn't have an > > equivalent for the command line -W option. Do people feel it would be > > useful to have a directive in mod_wsgi which allows one to control the > > warnings mechanism, ie., does the same as -W? > > It's probably useful. Frankly, though, I'm only using mod_wsgi for > production, not development, and I'd never let code spewing warnings > make its way into production. So doesn't help/hurt me personally, but > it's probably useful for less strict development environments.
I think it would be worthwhile if not too painful to add, Graham. I like the recent post you did on Django development under mod_wsgi and want to encourage people to use that more frequently Being able to see warnings the framework will raise in development is pretty important (otherwise, they'd be errors, not warnings), so that will help there. By the way, for those not following what Graham's written, (a) shame on you! and (b) see http://blog.dscpl.com.au/2008/12/using-modwsgi-when-developing-django.html and http://blog.dscpl.com.au/2009/02/source-code-reloading-with-modwsgi-on.html Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
