#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
Comment:
Hey David. I'll reclose since it's best to take these kind of discussions
to the DevelopersMailingList (as per the
[https://docs.djangoproject.com/en/3.2/internals/contributing/triaging-
tickets#s-id2 triage guidelines for wontfix tickets])
My thought was that really System Checks should be able to run in any
order — like `--random` for a test runner — that was my point about
''Indeed it might be a feature...''. Maybe that's not right though, so
seeing what a wider audience think may be worthwhile.
> ...bugs caused by different import orders ...
I don't know but, my thought here is that ordering the system checks is at
best a band-aid over a deeper problem here. Import order isn't really
something that's under user-control. Relying on it seems to be asking for
trouble... — but maybe others can speak differently.
--
Ticket URL: <https://code.djangoproject.com/ticket/33140#comment:3>
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.6f25a6c756e7afe7bf622a62e336efa6%40djangoproject.com.
