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

Yes, it can be done like that... I made it as a monkey patch because it might be that in the future Django's ContentType starts returning correct models using get_for_model() with proxied models, and then all well have to do is removing the patch and the "_proxied". That was my logic behind using a monkey patch.

On Dec 9, 2011, at 5:46 AM, Chris Glass wrote:

> How about putting get_for_proxied_model() somewhere else? Does it really have to live as a monkeypatch on a django base class? It just seems a bit... strange to maintain.
>
> Like using the function directly, or creating a polymorphic object that holds the method (so that you can use it as cache as well). Was the idea to piggy-back on the already existing self.__class__._cache ?
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/Kronuz/django_polymorphic/commit/e7d70a3616ed7ac753a6445af44b6e6ee37e674d#commitcomment-781813