#32971: System check methods can yield their items instead of creating lists at
every layer
-------------------------------------+-------------------------------------
Reporter: Chris Jerdonek | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Core (System | Version: dev
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 Mariusz Felisiak):
* status: new => closed
* resolution: => wontfix
Comment:
Thanks for this proposition, however it's
[https://docs.djangoproject.com/en/3.2/topics/checks/ documented] that
check function must return a **list** of messages. Also, folks can extend
checks at any level, see
[https://docs.djangoproject.com/en/3.2/topics/checks/#field-model-manager-
and-database-checks examples]. I don't think it's worth backward
compatibility concerns.
--
Ticket URL: <https://code.djangoproject.com/ticket/32971#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.2bc82e77696cf196ea592aafa06b0f08%40djangoproject.com.
