mirror of
https://github.com/django/django.git
synced 2025-08-04 02:48:35 +00:00
Removed versionadded/changed annotations for 2.1.
This commit is contained in:
parent
eb0ce6fa36
commit
ec7e179aeb
25 changed files with 0 additions and 208 deletions
|
@ -148,11 +148,6 @@ And on databases that support distinct on fields (such as PostgreSQL),
|
|||
|
||||
SELECT ... DISTINCT ON ABS("experiments"."change")
|
||||
|
||||
.. versionchanged:: 2.1
|
||||
|
||||
Ordering and distinct support as described in the last two paragraphs was
|
||||
added.
|
||||
|
||||
When looking for which lookups are allowable after the ``Transform`` has been
|
||||
applied, Django uses the ``output_field`` attribute. We didn't need to specify
|
||||
this here as it didn't change, but supposing we were applying ``AbsoluteValue``
|
||||
|
|
|
@ -144,12 +144,6 @@ decorator on your :meth:`~BaseCommand.handle` method::
|
|||
Since translation deactivation requires access to configured settings, the
|
||||
decorator can't be used for commands that work without configured settings.
|
||||
|
||||
.. versionchanged:: 2.1
|
||||
|
||||
The ``@no_translations`` decorator is new. In older versions, translations
|
||||
are deactivated before running a command unless the command's
|
||||
``leave_locale_alone`` attribute (now removed) is set to ``True``.
|
||||
|
||||
Testing
|
||||
=======
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue