#30938: DEFAULT_CONTENT_TYPE django.utils.deprecation.RemovedInDjango30Warning
-----------------------------------------+------------------------
Reporter: אורי | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 2.2
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 |
-----------------------------------------+------------------------
I'm upgrading Django from 1.11 to 2.2 in [https://github.com/speedy-net
/speedy-net Speedy Net]. I noticed that if I run `make_migrations` with
deprecation warnings (`./manage_all_sites_with_deprecation_warnings.sh
make_migrations`), I receive the following error message (with Django
2.2):
`django.utils.deprecation.RemovedInDjango30Warning: The
DEFAULT_CONTENT_TYPE setting is deprecated.`
Although I checked, and we don't use `DEFAULT_CONTENT_TYPE` anywhere in
our project. It's only used in Django.
You can see [https://travis-ci.org/speedy-net/speedy-net/jobs/605598271
this job] for example (with Python 3.5). If you check the jobs for Python
[https://travis-ci.org/speedy-net/speedy-net/jobs/605598272 3.6] and
[https://travis-ci.org/speedy-net/speedy-net/jobs/605598273 3.7], there is
another deprecation warning because of `distutils` which is used by
Django. This is since Django version 2.0. In Django 1.11 there are no
deprecation warnings with Python 3.5 and 3.6 (but there is
[https://code.djangoproject.com/ticket/30078 one] with Python 3.7).
--
Ticket URL: <https://code.djangoproject.com/ticket/30938>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/054.9fe719a20b06025dc67aeacb41c96465%40djangoproject.com.
