#33140: Enforce ordering of checks.
-------------------------------+--------------------------------------
Reporter: David Szotten | Owner: nobody
Type: New feature | Status: new
Component: Core (Other) | Version: 3.2
Severity: Normal | Resolution:
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 David Szotten):
* status: closed => new
* resolution: wontfix =>
Comment:
to be clear, i wasn't suggesting guaranteeing any _particular order, but
rather making sure the order is consistent between invocations and systems
django-typomatic was my example (and i fixed my issue by disabling the
checks for the management command in question), but the general problem is
hard-to-track-down bugs caused by different import orders on different
systems (in my case i have yet to figure out what even _caused the
iteration order to change)
(happy for you to re-close if you still think that's the best action here,
but wanted to clarify my suggestion)
--
Ticket URL: <https://code.djangoproject.com/ticket/33140#comment:2>
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.ff858a7984abcae8ef492b8875f1e2c2%40djangoproject.com.
