On Mon, May 17, 2010 at 5:29 PM, Alex Gaynor wrote:
> On Mon, May 17, 2010 at 10:00 AM, Charlie Nolan
> wrote:
> > It seems to me like the biggest problem with a settings module not
> > importing is that it's not safe to display a full error message about
> > that file. You can't tell if DEBUG
On Mon, May 17, 2010 at 10:00 AM, Charlie Nolan wrote:
> It seems to me like the biggest problem with a settings module not
> importing is that it's not safe to display a full error message about
> that file. You can't tell if DEBUG is on, and there may well be
> information in the settings that
It seems to me like the biggest problem with a settings module not
importing is that it's not safe to display a full error message about
that file. You can't tell if DEBUG is on, and there may well be
information in the settings that is a Bad Idea to leak on a production
server.
Also, as a friend
This also caused some heartache for me. I opened a ticket with a
simple patch here: http://code.djangoproject.com/ticket/13043. I'm
sure something more elaborate could be done, but simply printing the
ImportError in the console has been all I've needed thus far. Perhaps
you could update this tic
On Mon, May 17, 2010 at 6:10 AM, cool-RR wrote:
> Hello all.
>
> This is my first time on Django-developers.
>
> I remember that a few months ago, when I was doing some Django work,
> there was something that annoyed me. I hope I'm remembering this
> correctly, please correct me if I'm wrong. It h
Hello all.
This is my first time on Django-developers.
I remember that a few months ago, when I was doing some Django work,
there was something that annoyed me. I hope I'm remembering this
correctly, please correct me if I'm wrong. It happened sometimes that
the settings module in my project/app
