#27829: Deprecate DEFAULT_CONTENT_TYPE ------------------------------------------------+------------------------ Reporter: Adam Chainz | Owner: nobody Type: Cleanup/optimization | Status: new Component: HTTP handling | Version: 1.11 Severity: Normal | Keywords: Triage Stage: Unreviewed | Has patch: 0 Needs documentation: 0 | Needs tests: 0 Patch needs improvement: 0 | Easy pickings: 0 UI/UX: 0 | ------------------------------------------------+------------------------ After a [https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg /django-developers/EdwwxxqcKVU/oRcz4bbUAgAJ mailing list discussion] there was consensus that the {{{DEFAULT_CONTENT_TYPE}}} setting is no longer useful since HTML5 has overtaken XHTML and that it could be deprecated.
For reference, the setting has lead to a number of bug reports such as the one that kicked off the discussion, #23908, and others such as #24598, #20822, #11683, #5704, etc. -- Ticket URL: <https://code.djangoproject.com/ticket/27829> 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/053.59e55a43f0cbcf10a84d769e3a7a48f6%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.