- Language: en
- Documentation version: development
Django 3.0 release notes - UNDER DEVELOPMENT¶
Expected December 2019
Welcome to Django 3.0!
These release notes cover the new features, as well as some backwards incompatible changes you’ll want to be aware of when upgrading from Django 2.2 or earlier. We’ve dropped some features that have reached the end of their deprecation cycle, and we’ve begun the deprecation process for some features.
See the Upgrading Django to a newer version guide if you’re updating an existing project.
Django 3.0 supports Python 3.6, 3.7, and 3.8. We highly recommend and only officially support the latest release of each series.
The Django 2.2.x series is the last to support Python 3.5.
Third-party library support for older version of Django¶
Following the release of Django 3.0, we suggest that third-party app authors
drop support for all versions of Django prior to 2.2. At that time, you should
be able to run your package’s tests using
python -Wd so that deprecation
warnings appear. After making the deprecation warning fixes, your app should be
compatible with Django 3.0.
What’s new in Django 3.0¶
- Allowed MySQL spatial lookup functions to operate on real geometries. Previous support was limited to bounding boxes.
- The new
compilemessages --ignoreoption allows ignoring specific directories when searching for
.pofiles to compile.
Requests and Responses¶
- The new test
raise_request_exceptionallows controlling whether or not exceptions raised during the request should also be raised in the test. The value defaults to
Truefor backwards compatibility. If it is
Falseand an exception occurs, the test client will return a 500 response with the attribute
exc_info, a tuple providing information of the exception that occurred.
Backwards incompatible changes in 3.0¶
Database backend API¶
This section describes changes that may be needed in third-party database backends.
- The second argument of
DatabaseIntrospection.get_geometry_type()is now the row description instead of the column name.
DatabaseIntrospection.get_field_type()may no longer return tuples.
- If the database can create foreign keys in the same SQL statement that adds a
SchemaEditor.sql_create_column_inline_fkwith the appropriate SQL; otherwise, set
DatabaseFeatures.can_create_inline_fk = False.
can_return_ids_from_bulk_insertare renamed to
- Support for PostGIS 2.1 is removed.
- Support for SpatiaLite 4.1 and 4.2 is removed.
- Support for GDAL 1.11 and GEOS 3.4 is removed.
Dropped support for PostgreSQL 9.4¶
Upstream support for PostgreSQL 9.4 ends in December 2019. Django 3.0 supports PostgreSQL 9.5 and higher.
Dropped support for Oracle 12.1¶
Upstream support for Oracle 12.1 ends in July 2021. Django 2.2 will be supported until April 2022. Django 3.0 officially supports Oracle 12.2 and 18c.
Removed private Python 2 compatibility APIs¶
While Python 2 support was removed in Django 2.0, some private APIs weren’t removed from Django so that third party apps could continue using them until the Python 2 end-of-life.
Since we expect apps to drop Python 2 compatibility when adding support for Django 3.0, we’re removing these APIs at this time.
django.test.utils.str_prefix()- Strings don’t have ‘u’ prefixes in Python 3.
django.utils.lru_cache.lru_cache()- Alias of
django.utils.decorators.available_attrs()- This function returns
django.utils.decorators.ContextDecorator- Alias of
django.utils._os.abspathu()- Alias of
npath()- These functions do nothing on Python 3.
django.utils.six- Remove usage of this vendored library or switch to six.
django.utils.encoding.python_2_unicode_compatible()- Alias of
functools.partialmethod. See 5b1c389603a353625ae1603.
django.utils.safestring.SafeBytes- Unused since Django 2.0.
New default value for the
In older versions, the
FILE_UPLOAD_PERMISSIONS setting defaults to
None. With the default
FILE_UPLOAD_HANDLERS, this results in
uploaded files having different permissions depending on their size and which
upload handler is used.
FILE_UPLOAD_PERMISSION now defaults to
0o644 to avoid this
ContentType.__str__()now includes the model’s
app_labelto disambiguate model’s with the same name in different apps.
- Because accessing the language in the session rather than in the cookie is
LocaleMiddlewareno longer looks for the user’s language in the session and
django.contrib.auth.logout()no longer preserves the session’s language after logout.
Features deprecated in 3.0¶
force_text() aliases (since Django 2.0) of
force_str() are deprecated. Ignore this deprecation if
your code supports Python 2 as the behavior of
force_str() is different there.
urlunquote_plus()are deprecated in favor of the functions that they’re aliases for:
ungettext_lazy()are deprecated in favor of the functions that they’re aliases for:
- To limit creation of sessions and hence favor some caching strategies,
django.views.i18n.set_language()will stop setting the user’s language in the session in Django 4.0. Since Django 2.1, the language is always stored in the
Features removed in 3.0¶
These features have reached the end of their deprecation cycle and are removed in Django 3.0.
See Features deprecated in 2.0 for details on these changes, including how to remove usage of these features.
django.db.backends.postgresql_psycopg2module is removed.
DEFAULT_CONTENT_TYPEsetting is removed.
- Support for the
field_namekeyword argument of
QuerySet.earliest()` and ``latest()is removed.
See Features deprecated in 2.1 for details on these changes, including how to remove usage of these features.
ForceRHRGIS function is removed.
admin_statictemplate tag libraries are removed.