Kronuz/django_polymorphic — comment on commit e7d70a3616ed7ac753a6445af44b6e6ee37e674d
File: polymorphic/__init__.py line 52
By Kronuz:

The thing is they (at django) are not yet convinced `ContentType.objects.get_for_model()` should return proxied models, which in my opinion it should (there's a ticket about contrib `comments` app not working as expected on comments for proxied objects, because it uses the current `get_for_model()`)

Anyway, only code that explicitly makes use of `ContentType.objects.get_for_model()` on polymorphic models for something would "break" (we should add a backwards incompatibility note somewhere)

I'm using it with older code in production, as I was in the need of having proxied models, and I don't recall having to change any single line of code in my apps... lucky me I didn't use (or see the need to use) `ContentType.objects.get_for_model()` for my models. I needed to do a migration to remove unneeded tables for proxied models, but that I believe it's all, all those tables had was the `id`.