This is a discussion for https://code.djangoproject.com/ticket/31681 - the 
feature would be useful to me and seems like something generally useful as 
well since it is implemented in the testing framework.  The closing comment 
mentions that copying a documentation page into command output isn't 
valuable.  That isn't what I meant to suggest so I will attempt to explain 
more clearly below:

It would be helpful if `checks` would output what checks it is running.  
Currently you don't actually know if a check runs or not.  Perhaps it isn't 
registered correctly?  Or it was excluded by mistake when you expected it 
to run?  I like to keep this information around in build history for quick 
inspection purposes as needed.


For example, when running a check it would be nice to (optionally) see 
something of the form:

   - path.to.my.checkA ... ok
   - path.to.my.checkB ... ERROR
   - path.to.my.checkC ... ok
   - path.to.my.checkD ... WARN

System check ran 100 checks and identified 2 issues (0 silenced).

 

It would be helpful if the `checks` verbosity flag worked in similar 
fashion to the testing framework.  I am thinking that `-v 1` or unspecified 
would maintain the current behavior.  `-v 2` outputs all checks run not 
under the django namespace (due to the comment in the ticket about not 
repeating a documentation page).  And `-v 3` outputs all checks.  It might 
also be helpful to add a verbosity level that only prints checks under the 
current working directory (i.e. project specific checks) but this might be 
difficult to determine correctly based on project layout and installation 
method.

If the general consensus likes the feature and the issue can be re-opened, 
I will investigate.  The ticket says it would not be feasible to output 
this information.  I am assuming (since they are run generically via a 
registration approach) that it should be straightforward to log the dotted 
path of the check.

Please let me know what you think!

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/85259884-52fa-42b2-822f-f0537f5b2f0bo%40googlegroups.com.
  • ... Gordon
    • ... Adam Johnson
    • ... '1337 Shadow Hacker' via Django developers (Contributions to Django itself)

Reply via email to