#23959: Systems checks run when DEBUG is False
--------------------------------------+------------------------------------
Reporter: IanLewis | Owner: nobody
Type: Bug | Status: new
Component: Core (System checks) | Version: 1.7
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by freakboy3742):
* stage: Unreviewed => Accepted
Comment:
I think this is a hangover of some design decisions that were preserved in
spirit, but not in reality. Essentially, we wanted to make sure checks
wouldn't be run as part of the production stack; roughly speaking, that
means "DEBUG=False", but in practice, it really means that the checks
aren't run as part of the WSGI stack that is used to deploy the site.
The checks will still run in production as part of syncdb etc, but those
aren't performance critical operations, so the overhead (such as it is)
doesn't matter.
So - it isn't really "won't run if DEBUG is False", it's "won't run as
part of your production deployment stack".
--
Ticket URL: <https://code.djangoproject.com/ticket/23959#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.d49b40256158ad714327a1fdedabf1ec%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
