feedgenerator classes still use "mime_type" instead of "content_type"

[Charlie DeTar]

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:

    response = HttpResponse(content_type=feed.mime_type)

Might be aesthetically nicer to make this more consistent by using content_type across the board.

[Tim Graham]

Yes, but of course a deprecation of the current names is required. See ​Deprecating a Feature for a checklist of things to do when writing the patch.

[Raphael Michel]

I renamed the attributes and started the deprecation in this pull request: ​https://github.com/django/django/pull/4760

[Tim Graham <timograham@…>]

In 5c125f6:

Fixed #24728 -- Renamed mime_type to content_type for syndication feeds

Renamed the mime_type properties of RssFeed and Atom1Feed to
content_type and start deprecation for the old names.

[Tim Graham <timograham@…>]

In c6de8cc:

Refs #24728 - Removed Atom1Feed/RssFeed mime_type attribute.

Per deprecation timeline.