I read the original request as a matter of principle and not something born from an actual need.
View is intended to be the rightmost class in an inheritance scheme. I haven't seen a sane use case for injecting it as a mixin. This change is more likely to allow beginners to shoot themselves into the foot with an ill-conceived inheritance scheme than the status quo is to prevent advanced and interesting uses. In general I'm not eager to make constructs without practical value possible. Read this as a -0. -- Aymeric. -- You received this message because you are subscribed to the Google Groups "Django developers" 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]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/367C1BCA-2446-4C59-9FA4-CCDFBB6476B8%40polytechnique.org. For more options, visit https://groups.google.com/groups/opt_out.
