Ok, understood. All I wanted was discussion (or dismissal by simple matter of reason as your latest reply and my subsequent new understanding of the dev server's relationship to an application implies) about my original post. The thread started out with Jacob basically saying, "there's your solution, simple as that..." without even basically understanding my question, or reading it for that matter. Again, I apologize for the now 22 post long digression.
On Sep 26, 1:52 am, Russell Keith-Magee <russ...@keith-magee.com> wrote: > On Sunday, September 26, 2010, Yo-Yo Ma <baxterstock...@gmail.com> wrote: > > I apologize Russell. There's been a gross understanding of what I was > > asking. I'm not asking how to do "if settings.debug: x = y". I'm > > asking for a way to set settings.debug to true dynamically without > > having to rely on deployment specific issues. Ie, pass a variable in > > when the dev server is run (by default) that allows you to set > > settings.debug to true. > > And we keep telling you that such a setting doesn't make much sense. > > The development server isn't special - it runs code the same way as > any other server, just without the overhead of a full production > server. I can't see any compelling reason to embed a special > 'development mode' status into the development server. After all, you > can develop Django code without using the dev server. > > If you want to force DEBUG=True when you use the dev server, you > already can do this by specifying a different settings.py file when > you start the dev server. This works right now, and doesn't require > imbuing the dev server with special status. > > Yours, > Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
