Future backwards-incompatible changes

Now that Django has reached version 1.0, we are strongly committed to backwards-compatibility. But we continue to refactor and improve Django's codebase so that it will be even better in the future.

This page lists backwards-incompatible changes that will happen for Django 2.0. Although version 2.0 may not be released for a long time, this page exists so that Django's developers can keep track of code they've refactored that should be deprecated and cleaned up for version 2.0.

See also: BackwardsIncompatibleChanges

Moved django.views.defaults.shortcut to django.contrib.contenttypes.views.shortcut

Initial change made in [9001].

With the goal of removing all django.contrib references from the core Django codebase, the shortcut() function in django/views/defaults.py has been moved to django/contrib/contenttypes/views.py.