#23444: Legacy code unnecessarily creates ContentType object for `through` model when using it in inlines --------------------------------------+------------------------------------ Reporter: a1tus | Owner: nobody Type: Cleanup/optimization | Status: new Component: contrib.admin | Version: master Severity: Normal | Resolution: Keywords: | Triage Stage: Accepted Has patch: 0 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 --------------------------------------+------------------------------------
Comment (by timgraham): I don't think a method is really needed, but you could use an underscore method (`_original_content_type_id`) and assign it to `original_content_type_id` in `__init__()` if you want. The class to use is `RemovedInDjango20Warning`, see the [https://docs.djangoproject.com/en/dev/internals/contributing/writing-code /submitting-patches/#deprecating-a-feature Deprecating a feature] guide for details. -- Ticket URL: <https://code.djangoproject.com/ticket/23444#comment:5> 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 unsubscribe from this group and stop receiving emails from it, send an email to django-updates+unsubscr...@googlegroups.com. To post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/063.1d49c042570e5002551f6252d5d358f5%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.