#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 akaariai):
I don't know if they should share the contenttype or not. Not my
expertise. I guess if contenttypes are generated for the proxy models in
syncdb, then proxy models have their own contenttypes, otherwise not. No
strong opinions to either direction. Maybe ask django-developers?
The best to do for checking DRY chances is doing a project-wide grep for
proxy_for_model. Git grep is wonderful for this. I have a feeling I have
already done this once in some ticket, but can't find it and can't
remember what it was related to...
--
Ticket URL: <https://code.djangoproject.com/ticket/17648#comment:9>
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.
