➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Retro
Recipients Retro, docs@python, dontknow, ezio.melotti, georg.brandl, skrah, terry.reedy
Date 2012-01-23.14:26:52
SpamBayes Score 5.927744e-06
Marked as misclassified No
Message-id <1327328813.16.0.598727660248.issue13816@psf.upfronthosting.co.za>
In-reply-to
Content 
Ah, darn it! My last patch is a total garbage. But then an interesting thing happened: I wanted to delete my last patch set, but I got a

"ProgrammingError at /review/13816/patchset/4039/delete
schema "datetime" does not exist"

and got all the Django nitty-gritty info about your server. This is not good because someone can misuse that information. Please fix this. You have "DEBUG = True" set and so all the details of your server is leaked. Better change that to "DEBUG = False" and let the user get a standard 500 error page instead.

It says at the bottom: "You're seeing this error because you have DEBUG = True in your Django settings file. Change that to False, and Django will display a standard 500 page."
History
Date User Action Args
2012-01-23 14:26:53Retrosetrecipients: + Retro, georg.brandl, terry.reedy, ezio.melotti, skrah, docs@python, dontknow
2012-01-23 14:26:53Retrosetmessageid: <1327328813.16.0.598727660248.issue13816@psf.upfronthosting.co.za>
2012-01-23 14:26:52Retrolinkissue13816 messages
2012-01-23 14:26:52Retrocreate