#30179: Merging 3 or more media objects can throw unnecessary
MediaOrderConflictWarnings
-------------------------------+------------------------------------
Reporter: Matt Westcott | Owner: nobody
Type: Bug | Status: new
Component: Forms | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------------------
Comment (by Matthias Kestenholz):
Thinking some more:
- `sorted()` is more likely to break existing code because people probably
haven't listed all dependencies in their `js` attributes now. Yes, that's
not what they should have done, but breaking peoples' projects sucks and I
don't really want to do that (even if introducing `sorted()` might be the
least disruptive and at the same time most correct change)
- wanting to handle the `jquery`, `widget1`, `noConflict` and `jquery`,
`widget2`, `noConflict` case has introduced an unexpected amount of
complexity
- introducing a complex solving framework will have a really bad impact on
runtime and will introduce even more complexity and is out of the question
to me
I'm happy to help fixing this but right now I only see bad and worse
choices.
--
Ticket URL: <https://code.djangoproject.com/ticket/30179#comment:6>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.030104e3c1a83d7dc46c845d6a2e0760%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
