#19345: ContentType.objects.get_for_model shouldn't create missing content types
-------------------------------------+-------------------------------------
Reporter: aaugustin | Owner: nobody
Type: Bug | Status: new
Component: | Version: master
contrib.contenttypes | Resolution:
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by ptone):
Seems that this behavior is fully intentional and long standing based on
code comments and git-blame.
Given that as you say - this is mostly a non-issue either way under normal
usage, and there is a slim chance that the backwards incompatible change
to raise an error could cause some edge case breakage - wouldn't it be
better to leave as is and just access the ContentType model through
standard manager methods?
Basically - is this worth changing?
--
Ticket URL: <https://code.djangoproject.com/ticket/19345#comment:1>
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 https://groups.google.com/groups/opt_out.
