On Friday, 13 January 2017 19:22:13 UTC+11, Aymeric Augustin wrote: > > I agree that this setting has become less useful now that <!DOCTYPE html> > has won. > > It made more sense when it wasn’t clear whether XHTML1.1 would take over > HTML4. > > I’d be interested to hear about use cases, if someone still uses it and > reads this. >
Sorry for delay in responding. If you depreciate `DEFAULT_CONTENT_TYPE` I am not sure what you plan to do instead? Would Django hard code "text/html" as the default? I hadn't realised that the XHTML standards are basically dead (and doesn't appear to be supported in HTML5), in which case this probably makes sense. Thanks -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/c04be7c1-6ade-469c-b97c-0499598d2084%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
