Hi,
I took a look at PR 2192[1] earlier, and noted that checks.register keeps
being used as a function, called from AppConfig.ready(), and not as a
decorator; but it is defined as a decorator, so it looks a little funny:
checks.register('models')(check_generic_foreign_keys)
(from the contenttypes AppConfig, for example).
Registering checks only in ready(), rather than at import time, is now the way
to do things, so register() should typically not be used as a decorator; I
think we should change its definition accordingly, to
def register(self, check, *tags)
Thoughts?
[1] https://github.com/django/django/pull/2192
--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/201401230229.31275.shai%40platonix.com.
For more options, visit https://groups.google.com/groups/opt_out.
