[Django] #31681: Output checks ran via manage.py checks
Django
-----------------------------------------+------------------------
Reporter: thenewguy | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 3.0
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-----------------------------------------+------------------------
It would be helpful to have the checks framework output the checks that
are run. In some situations output that can be inspected to verify a
particular check was actually run is very helpful. As such, having this
in CI logs is quite useful - perhaps behind a verbosity flag like the test
command uses (-v 2)?
--
Ticket URL: <https://code.djangoproject.com/ticket/31681>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
-------------------------------------+-------------------------------------
Reporter: thenewguy | Owner: nobody
Type: New feature | Status: closed
Component: Core (System | Version: master
checks) |
Severity: Normal | Resolution: wontfix
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 felixxm):
* status: new => closed
* type: Uncategorized => New feature
* component: Uncategorized => Core (System checks)
* version: 3.0 => master
* resolution: => wontfix
Comment:
Thanks for this ticket, however system checks are a set of conditions
checked inside many methods, that's why it will be really complicated
(maybe even not feasible) to list them when running `django-admin checks`.
Moreover `django-admin checks` runs all checks in selected tags so I don't
think that copying a [https://docs.djangoproject.com/en/stable/ref/checks/
documentation page] to the management command output is valuable. You can
start a discussion on DevelopersMailingList if you don't agree.
--
Ticket URL: <https://code.djangoproject.com/ticket/31681#comment:1>