#17648: Allow `ContentTypeManager` and `GenericForeignKey` to retreive/store
proxy
model content type.
-------------------------------------+-------------------------------------
Reporter: charettes | Owner: charettes
Type: Bug | Status: new
Component: | Version: SVN
contrib.contenttypes | Resolution:
Severity: Normal | Triage Stage: Design
Keywords: contenttype proxy | decision needed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by charettes):
Is there any ticket concerning the `proxy_for_model` proxy chain issue
directly or are they all side issues? Do you think It would be worth
opening a ticket for this issue only?
I agree the `__bases__[0]` part is quite ugly but it was the only way
fixing this reliably since the proxy chain is broken and we can assume
that deferred models have only one base which is the model were trying to
refer to. But I also agree fixing the `proxy_for_model` chain issue would
be better.
--
Ticket URL: <https://code.djangoproject.com/ticket/17648#comment:6>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
