Changes between Version 2 and Version 3 of Ticket #16368, comment 16


Ignore:
Timestamp:
11/24/2013 04:15:05 PM (5 years ago)
Author:
Ramiro Morales
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #16368, comment 16

    v2 v3  
    33Bisection betwen 1.2 and 1.3 (the two releases the OP reports things changed from working to not working e.g. the custom Sites model gets replaced by the `contrib.sites` app one even when that app isn't listed in INSTALLED_APPS) shows the commit where that change in behavior appeared is r14769.
    44
    5 (Conditions are: Using the simple `foobar` project attached to this ticket and adding `django.contrib.contenttypes import generic` to its `sites/models.py` file).
     5(Conditions are: Using the simple `foobar` project attached to this ticket and adding `from django.contrib.contenttypes import generic` to its `sites/models.py` file).
    66
    77I don't think the changes from that commit in particular are wrong regarding this issue. Looking at the traceback in comment:12 IMHO what's the culprit of this unexpected behavior is the fact that `django.contrib.contenttypes.generic` contains both the definitions of the model-related generic stuff (!GenericForeignKey, etc.) AND the admin app-related specialized inlines (!GenericInlineModelAdmin, !GenericStackedInline, !GenericTabularInline.)
Back to Top