Professional Documents
Culture Documents
API stability
=============
At the same time as making API stability a very high priority, Django is also
committed to continual improvement, along with aiming for "one way to do it"
(eventually) in the APIs we provide. This means that when we discover clearly
superior ways to do things, we will deprecate and eventually remove the old
ways. Our aim is to provide a modern, dependable web framework of the highest
quality that encourages best practices in all projects that use it. By using
incremental improvements, we try to avoid both stagnation and large breaking
upgrades.
- All the public APIs (everything in this documentation) will not be moved
or renamed without providing backwards-compatible aliases.
- If, for some reason, an API declared stable must be removed or replaced, it
will be declared deprecated but will remain in the API for at least two
feature releases. Warnings will be issued when the deprecated method is
called.
Stable APIs
===========
Exceptions
==========
Security fixes
--------------