summaryrefslogtreecommitdiff
path: root/docs/ref/django-admin.txt
diff options
context:
space:
mode:
Diffstat (limited to 'docs/ref/django-admin.txt')
-rw-r--r--docs/ref/django-admin.txt37
1 files changed, 0 insertions, 37 deletions
diff --git a/docs/ref/django-admin.txt b/docs/ref/django-admin.txt
index 41df95b37a..a48a7043fd 100644
--- a/docs/ref/django-admin.txt
+++ b/docs/ref/django-admin.txt
@@ -132,8 +132,6 @@ List all available tags.
.. django-admin-option:: --deploy
-.. versionadded:: 1.8
-
The ``--deploy`` option activates some additional checks that are only relevant
in a deployment setting.
@@ -172,10 +170,6 @@ into compiled files.
``compilemessages`` now matches the operation of :djadmin:`makemessages`,
scanning the project tree for ``.po`` files to compile.
-.. versionchanged:: 1.8
-
- Added ``--exclude`` and ``--use-fuzzy`` options.
-
Example usage::
django-admin compilemessages --locale=pt_BR
@@ -312,8 +306,6 @@ one model.
.. django-admin-option:: --output
-.. versionadded:: 1.8
-
By default ``dumpdata`` will output all the serialized data to standard output.
This option allows you to specify the file to which the data is to be written.
When this option is set and the verbosity is greater than 0 (the default), a
@@ -418,10 +410,6 @@ models that may have been removed since the fixture was originally generated.
The :djadminopt:`--app` option can be used to specify a single app to look
for fixtures in rather than looking through all apps.
-.. versionchanged:: 1.8
-
- ``--ignorenonexistent`` also ignores non-existent models.
-
What's a "fixture"?
~~~~~~~~~~~~~~~~~~~
@@ -587,8 +575,6 @@ Separate multiple extensions with commas or use -e or --extension multiple times
Use the :djadminopt:`--locale` option (or its shorter version ``-l``) to
specify the locale(s) to process.
-.. versionadded:: 1.8
-
Use the :djadminopt:`--exclude` option (or its shorter version ``-x``) to
specify the locale(s) to exclude from processing. If not provided, no locales
are excluded.
@@ -698,15 +684,11 @@ The ``--merge`` option enables fixing of migration conflicts.
.. django-admin-option:: --name, -n
-.. versionadded:: 1.8
-
The ``--name`` option allows you to give the migration(s) a custom name instead
of a generated one.
.. django-admin-option:: --exit, -e
-.. versionadded:: 1.8
-
The ``--exit`` option will cause ``makemigrations`` to exit with error code 1
when no migrations are created (or would have been created, if combined with
``--dry-run``).
@@ -749,8 +731,6 @@ run correctly.
.. django-admin-option:: --fake-initial
-.. versionadded:: 1.8
-
The ``--fake-initial`` option can be used to allow Django to skip an app's
initial migration if all database tables with the names of all models created
by all :class:`~django.db.migrations.operations.CreateModel` operations in that
@@ -970,8 +950,6 @@ showmigrations [<app_label> [<app_label>]]
.. django-admin:: showmigrations
-.. versionadded:: 1.8
-
Shows all migrations in a project.
.. django-admin-option:: --list, -l
@@ -1238,8 +1216,6 @@ expected to run from. The default value is ``localhost:8081-8179``.
.. django-admin-option:: --keepdb
-.. versionadded:: 1.8
-
The ``--keepdb`` option can be used to preserve the test database between test
runs. This has the advantage of skipping both the create and destroy actions
which can greatly decrease the time to run tests, especially those in a large
@@ -1249,8 +1225,6 @@ be applied to the test database before running the test suite.
.. django-admin-option:: --reverse
-.. versionadded:: 1.8
-
The ``--reverse`` option can be used to sort test cases in the opposite order.
This may help in debugging the side effects of tests that aren't properly
isolated. :ref:`Grouping by test class <order-of-tests>` is preserved when using
@@ -1258,8 +1232,6 @@ this option.
.. django-admin-option:: --debug-sql
-.. versionadded:: 1.8
-
The ``--debug-sql`` option can be used to enable :ref:`SQL logging
<django-db-logger>` for failing tests. If :djadminopt:`--verbosity` is ``2``,
then queries in passing tests are also output.
@@ -1428,8 +1400,6 @@ it when running interactively.
Use the ``--database`` option to specify the database into which the superuser
object will be saved.
-.. versionadded:: 1.8
-
You can subclass the management command and override ``get_input_data()`` if you
want to customize data input and validation. Consult the source code for
details on the existing implementation and the method's parameters. For example,
@@ -1767,13 +1737,6 @@ Named arguments can be passed by using either one of the following syntaxes::
# `use_natural_foreign_keys` is the option destination variable
management.call_command('dumpdata', use_natural_foreign_keys=True)
-.. versionchanged:: 1.8
-
- The first syntax is now supported thanks to management commands using the
- :py:mod:`argparse` module. For the second syntax, Django previously passed
- the option name as-is to the command, now it is always using the ``dest``
- variable name (which may or may not be the same as the option name).
-
Command options which take multiple options are passed a list::
management.call_command('dumpdata', exclude=['contenttypes', 'auth'])