Changes between Version 6 and Version 7 of Ticket #27317, comment 3


Ignore:
Timestamp:
Oct 7, 2016, 5:05:31 PM (8 years ago)
Author:
James Pic

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #27317, comment 3

    v6 v7  
    11> ​As the documentation says about Meta, "Normal Python name resolution rules apply. If you have multiple base classes that declare a Meta inner class, only the first one will be used.
    22
    3 Oh, I was talking about Media, not Meta... I don't see any case where you'd want to render a widget or form without a certain script that it requires, users would just end with broken forms or is there any other result possible from this ? I'm thinking that if Form.Media inherits from the Widget Media because they require it to function properly, not because it would be nice to have. But I might be missing something again like the explicit inheritance design decision in my initial report.
     3Oh, I was talking about Media, not Meta... I don't see any case where you'd want to render a widget or form without a certain script that it requires, users would just end with broken forms or is there any other result possible from this ?
     4
     5> Can you think of any precedents in Django where automatic merging similar to what you proposed takes place?
     6
     7I'm thinking that if Form.Media inherits from the Widget Media because they require it to function properly, not because it would be nice to have. But I might be missing something again like the explicit inheritance design decision in my initial report.
    48
    59Even if the paralogism between Form.Meta and Form.Media is valid (which I recon I didn't check), explicit inheritance doesn't fix it:
Back to Top