#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 Matt Westcott):

 I don't think sorting by length is the way to go - it would be trivial to
 make the test fail again by extending the first list with unrelated items.
 It //might// be a good real-world heuristic for finding a solution more
 often, but that's just trading a reproducible bug for an unpredictable
 one.

 (I'm not sure I'd trust it as a heuristic either: we've encountered this
 issue on Wagtail CMS, where we're making extensive use of form media on
 hierarchical form structures, and so those media definitions will tend to
 bubble up several layers to reach the top level. At that point, there's no
 way of knowing whether the longer list is the one with more complex
 dependencies, or just one that collected more unrelated files on the way
 up the tree...)

 I'll do some more thinking on this. My hunch is that even if it does end
 up being a travelling-salesman-type problem, it's unlikely to be run on a
 large enough data set for performance to be an issue.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/30179#comment:7>
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.396382e3d9a36fe1a87720a4cf421146%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to