#33140: Enforce ordering of checks.
-------------------------------+--------------------------------------
Reporter: David Szotten | Owner: nobody
Type: New feature | Status: closed
Component: Core (Other) | Version: 3.2
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 Carlton Gibson):
* status: new => closed
* resolution: => wontfix
* type: Uncategorized => New feature
* component: Uncategorized => Core (Other)
Comment:
Hi David.
I don't think it's really part of the System Check API/contract that
they're run in any order. I don't think making it such is a good idea.
(Indeed it might be a feature that they're not...) We could throw in the
`sorted` — what would it hurt? — but then folks would end up
using/depending on it. As such I'm inclined to `wontfix`.
The change from the PR was so long ago now I can't see a realistic case
for arguing there's a regression here. A set was the right collection type
all along.
So to your problem, I think a change in `django-typomatic` is the way to
go. Even if we accepted this here it would be roughly a year before it was
isn an available version of Django. Applying some kind of sort in `django-
typomatic`, on the other hand, could be available ≈immediately, and it's
probably something it should do anyway…
--
Ticket URL: <https://code.djangoproject.com/ticket/33140#comment:1>
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/070.9369671772c6636f71e146435f415706%40djangoproject.com.
