Unfortunately, I'm a bit late. I didn't suspected that polishing code after review takes so much time. Lots of my work from last Wednesday was small improvements, but there are some vital changes:
The API will be consistent with API of logging module or message framework. Being consistent means that system check framework will be familiar to lots of developers. The change is that every message has its `level` now -- one of CRITICAL, ERROR, WARNING, INFO or DEBUG integer values. Django users may add their own levels (like SUPER_CRITICAL) since `level` is an integer. This change affected output format. All messages are sorted by level (and then by source of problem), so critical errors are first on the list and there is no opportunity to miss an important error in the middle of long list of warnings. There is some stuff that still need to be done as part of reviewing, i. e. deprecating `BaseCommand.validate` in favour of `check` or adding tests for `GenericForeignKey`. After finishing polishing I will focus on moving custom User model checks to auth apps, and then on rewritting admin checks. Note that there is a lot of discussion on the pull request [1]. [1] https://github.com/django/django/pull/1364 -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
