[Django] #25234: Possibility to disable System Checks
Django
--------------------------------------------+--------------------
Reporter: marcinn | Owner: nobody
Type: New feature | Status: new
Component: Core (Management commands) | Version: 1.8
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------------+--------------------
I need to disable whole system checks. I don't need them. Silencing is not
a solution, because still prints lots of unwanted messages and slowdowns
command`s startup.
You can add condition based on `DISABLE_SYSTEM_CHECKS` setting in
`django.core.checks.registry.CheckRegistry.run_checks`:
{{{
def run_checks(self, app_configs=None, tags=None,
include_deployment_checks=False):
""" Run all registered checks and return list of Errors and
Warnings.
"""
if getattr(settings, 'DISABLE_SYSTEM_CHECKS', None):
return []
}}}
This should be enough to disable checks, but Django still prints out:
{{{
Performing system checks...
System check identified no issues (0 silenced).
}}}
I would like to make complete patch / pull requests, if you will accept an
idea o disabiling system checks.
--
Ticket URL: <https://code.djangoproject.com/ticket/25234>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
Reporter: marcinn | Owner: nobody
Type: New feature | Status: new
commands) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Changes (by charettes):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
What about re-using ` SILENCED_SYSTEM_CHECKS` with an `'__all__'` value
instead?
--
Ticket URL: <https://code.djangoproject.com/ticket/25234#comment:1>
Django
-------------------------------------+-------------------------------------
Reporter: marcinn | Owner: nobody
Type: New feature | Status: new
commands) |
Severity: Normal | Resolution:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Easy pickings: 0 | UI/UX: 0
Comment (by timgraham):
[https://groups.google.com/d/topic/django-
developers/vMH7CVGHldo/discussion django-developers discussion]
--
Ticket URL: <https://code.djangoproject.com/ticket/25234#comment:2>
Django
-------------------------------------+-------------------------------------
Type: New feature | Status: closed
Component: Core (Management | Version: 1.8
commands) |
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Easy pickings: 0 | UI/UX: 0
Changes (by timgraham):
* status: new => closed
* resolution: => wontfix
Comment:
I'm not yet convinced there is a strong demand for disabling all checks
instead of disabling the ones that you don't find useful or give false-
positives on your project. Will happily reopen if the mailing list
discussion decides otherwise.
--
Ticket URL: <https://code.djangoproject.com/ticket/25234#comment:3>
Django
-------------------------------------+-------------------------------------
Type: New feature | Status: closed
Component: Core (Management | Version: 1.8
commands) |
Severity: Normal | Resolution: wontfix
| Unreviewed
Has patch: 0 | Needs documentation: 0
Easy pickings: 0 | UI/UX: 0
Comment (by cknoll):
Although this feature has been closed several years ago as *wontfix* it
seems like it has been fixed anyway. Quoting
[https://docs.djangoproject.com/en/4.1/ref/django-admin/#runserver]:
{{{
Changed in Django 4.0:
Support for the --skip-checks option was added.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/25234#comment:4>