#24728: feedgenerator classes still use "mime_type" instead of "content_type"
-------------------------------+--------------------
Reporter: yourcelf | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 1.8
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------
The `mimetype` argument to `HttpResponse` and others was deprecated in
v1.5 and removed in v1.7 in favor of `content_type` to be more
semantically aligned with the HTTP header it represents. However, the
feedgenerator classes `django.utils.feedgenerator.RssFeed` and
`django.utils.feedgenerator.Atom1Feed` still use a `mime_type` attribute.
This leads to slightly ungainly semantics like:
{{{#!python
response = HttpResponse(content_type=feed.mime_type)
}}}
Might be aesthetically nicer to make this more consistent by using
`content_type` across the board.
--
Ticket URL: <https://code.djangoproject.com/ticket/24728>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/051.b43c71382dd7bd696ec9cdea741182e9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
