From 54848a96dd4a196e81f3d71c61caf84ea8b49f4e Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Sat, 12 Sep 2015 16:27:30 -0400 Subject: [PATCH] Removed versionadded/changed annotations for 1.8. --- docs/howto/custom-lookups.txt | 4 -- docs/howto/custom-management-commands.txt | 9 --- docs/howto/custom-template-tags.txt | 11 --- docs/howto/writing-migrations.txt | 2 - .../writing-code/submitting-patches.txt | 6 -- .../contributing/writing-code/unit-tests.txt | 4 -- docs/ref/class-based-views/mixins-editing.txt | 10 --- .../mixins-multiple-object.txt | 4 -- docs/ref/class-based-views/mixins-simple.txt | 22 +----- .../mixins-single-object.txt | 8 +-- docs/ref/contrib/admin/index.txt | 28 -------- docs/ref/contrib/auth.txt | 16 ----- docs/ref/contrib/flatpages.txt | 5 -- docs/ref/contrib/gis/gdal.txt | 2 - docs/ref/contrib/gis/install/postgis.txt | 9 +-- docs/ref/contrib/gis/install/spatialite.txt | 5 -- docs/ref/contrib/gis/serializers.txt | 2 - docs/ref/contrib/postgres/index.txt | 2 - docs/ref/contrib/sitemaps.txt | 2 - docs/ref/contrib/sites.txt | 4 -- docs/ref/databases.txt | 15 ---- docs/ref/django-admin.txt | 37 ---------- docs/ref/exceptions.txt | 7 -- docs/ref/files/file.txt | 9 --- docs/ref/files/uploads.txt | 4 -- docs/ref/forms/api.txt | 13 ---- docs/ref/forms/fields.txt | 19 ----- docs/ref/forms/models.txt | 5 -- docs/ref/forms/widgets.txt | 22 +++--- docs/ref/middleware.txt | 4 -- docs/ref/migration-operations.txt | 21 ------ docs/ref/models/conditional-expressions.txt | 2 - docs/ref/models/database-functions.txt | 2 - docs/ref/models/expressions.txt | 21 ------ docs/ref/models/fields.txt | 18 ----- docs/ref/models/instances.txt | 8 --- docs/ref/models/lookups.txt | 2 - docs/ref/models/meta.txt | 11 --- docs/ref/models/options.txt | 2 - docs/ref/models/querysets.txt | 29 -------- docs/ref/request-response.txt | 22 ------ docs/ref/settings.txt | 70 +++---------------- docs/ref/signals.txt | 8 --- docs/ref/template-response.txt | 8 --- docs/ref/templates/api.txt | 14 ---- docs/ref/templates/builtins.txt | 15 +--- docs/ref/urls.txt | 5 -- docs/ref/utils.txt | 31 +------- docs/ref/validators.txt | 21 ------ docs/releases/1.7.txt | 5 -- docs/topics/auth/customizing.txt | 20 ++---- docs/topics/auth/default.txt | 2 - docs/topics/checks.txt | 6 -- .../class-based-views/generic-editing.txt | 10 --- docs/topics/conditional-view-processing.txt | 5 -- docs/topics/db/examples/many_to_one.txt | 7 -- docs/topics/db/examples/one_to_one.txt | 7 -- docs/topics/db/transactions.txt | 5 -- docs/topics/email.txt | 14 ---- docs/topics/forms/index.txt | 4 -- docs/topics/forms/modelforms.txt | 12 ---- docs/topics/http/middleware.txt | 5 -- docs/topics/http/sessions.txt | 6 -- docs/topics/http/shortcuts.txt | 8 --- docs/topics/i18n/formatting.txt | 6 -- docs/topics/i18n/translation.txt | 4 -- docs/topics/logging.txt | 2 - docs/topics/migrations.txt | 54 -------------- docs/topics/signals.txt | 10 +-- docs/topics/signing.txt | 4 -- docs/topics/templates.txt | 27 ------- docs/topics/testing/advanced.txt | 14 ---- docs/topics/testing/overview.txt | 23 ++---- docs/topics/testing/tools.txt | 36 +--------- 74 files changed, 44 insertions(+), 852 deletions(-) diff --git a/docs/howto/custom-lookups.txt b/docs/howto/custom-lookups.txt index f398618e395..51ddbbcd2fa 100644 --- a/docs/howto/custom-lookups.txt +++ b/docs/howto/custom-lookups.txt @@ -52,10 +52,6 @@ Lookup registration can also be done using a decorator pattern:: class NotEqualLookup(Lookup): # ... -.. versionchanged:: 1.8 - - The ability to use the decorator pattern was added. - We can now use ``foo__ne`` for any field ``foo``. You will need to ensure that this registration happens before you try to create any querysets using it. You could place the implementation in a ``models.py`` file, or register the lookup diff --git a/docs/howto/custom-management-commands.txt b/docs/howto/custom-management-commands.txt index ac89dd0ded1..f42680b6937 100644 --- a/docs/howto/custom-management-commands.txt +++ b/docs/howto/custom-management-commands.txt @@ -136,11 +136,6 @@ because some commands shipped with Django perform several tasks (for example, user-facing content rendering and database population) that require a project-neutral string language. -.. versionchanged:: 1.8 - - In previous versions, Django forced the "en-us" locale instead of - deactivating translations. - If, for some reason, your custom management command needs to use a fixed locale, you should manually activate and deactivate it in your :meth:`~BaseCommand.handle` method using the functions provided by the I18N @@ -226,8 +221,6 @@ All attributes can be set in your derived class and can be used in .. attribute:: BaseCommand.missing_args_message - .. versionadded:: 1.8 - If your command defines mandatory positional arguments, you can customize the message error returned in the case of missing arguments. The default is output by :py:mod:`argparse` ("too few arguments"). @@ -281,8 +274,6 @@ the :meth:`~BaseCommand.handle` method must be implemented. .. method:: BaseCommand.add_arguments(parser) - .. versionadded:: 1.8 - Entry point to add parser arguments to handle command line arguments passed to the command. Custom commands should override this method to add both positional and optional arguments accepted by the command. Calling diff --git a/docs/howto/custom-template-tags.txt b/docs/howto/custom-template-tags.txt index f44715a14a0..9294927cf2b 100644 --- a/docs/howto/custom-template-tags.txt +++ b/docs/howto/custom-template-tags.txt @@ -340,8 +340,6 @@ Template filter code falls into one of two situations: .. warning:: Avoiding XSS vulnerabilities when reusing built-in filters - .. versionchanged:: 1.8 - Django's built-in filters have ``autoescape=True`` by default in order to get the proper autoescaping behavior and avoid a cross-site script vulnerability. @@ -849,15 +847,6 @@ template yourself. For example:: t = context.template.engine.get_template('small_fragment.html') return t.render(Context({'var': obj}, autoescape=context.autoescape)) -.. versionchanged:: 1.8 - - The ``template`` attribute of ``Context`` objects was added in Django 1.8. - :meth:`context.template.engine.get_template - ` must be used instead of - :func:`django.template.loader.get_template` because the latter now returns - a wrapper whose ``render`` method doesn't accept a - :class:`~django.template.Context`. - If we had neglected to pass in the current ``context.autoescape`` value to our new ``Context`` in this example, the results would have *always* been automatically escaped, which may not be the desired behavior if the template diff --git a/docs/howto/writing-migrations.txt b/docs/howto/writing-migrations.txt index 5527302fa8b..842485adfd3 100644 --- a/docs/howto/writing-migrations.txt +++ b/docs/howto/writing-migrations.txt @@ -36,8 +36,6 @@ attribute:: migrations.RunPython(forwards), ] -.. versionadded:: 1.8 - You can also provide hints that will be passed to the :meth:`allow_migrate()` method of database routers as ``**hints``: diff --git a/docs/internals/contributing/writing-code/submitting-patches.txt b/docs/internals/contributing/writing-code/submitting-patches.txt index bc7503518f2..e845ab3d06a 100644 --- a/docs/internals/contributing/writing-code/submitting-patches.txt +++ b/docs/internals/contributing/writing-code/submitting-patches.txt @@ -207,12 +207,6 @@ level: class MyDeprecatedTests(unittest.TestCase): ... -.. versionchanged:: 1.8 - - Previous versions of Django had some ``Ignore*DeprecationWarningsMixin`` - classes to prevent warnings from appearing. These have been replaced by the - ``ignore_warnings`` decorator. - You can also add a test for the deprecation warning. You'll have to disable the "warning as error" behavior in your test by doing:: diff --git a/docs/internals/contributing/writing-code/unit-tests.txt b/docs/internals/contributing/writing-code/unit-tests.txt index 4acaa78c51a..cfad2f1db6a 100644 --- a/docs/internals/contributing/writing-code/unit-tests.txt +++ b/docs/internals/contributing/writing-code/unit-tests.txt @@ -282,10 +282,6 @@ combine this with ``--verbosity=2``, all SQL queries will be output:: $ ./runtests.py basic --debug-sql -.. versionadded:: 1.8 - - The ``--reverse`` and ``--debug-sql`` options were added. - By default tests are run in parallel with one process per core. You can adjust this behavior with the ``--parallel`` option:: diff --git a/docs/ref/class-based-views/mixins-editing.txt b/docs/ref/class-based-views/mixins-editing.txt index 832f42ccd4a..29e1f05a8ee 100644 --- a/docs/ref/class-based-views/mixins-editing.txt +++ b/docs/ref/class-based-views/mixins-editing.txt @@ -114,11 +114,6 @@ ModelFormMixin :exc:`~django.core.exceptions.ImproperlyConfigured` exception will be raised. - .. versionchanged:: 1.8 - - Previously if both ``fields`` and ``form_class`` were specified, - ``fields`` was silently ignored. - **Mixins** * :class:`django.views.generic.edit.FormMixin` @@ -142,11 +137,6 @@ ModelFormMixin result in an :exc:`~django.core.exceptions.ImproperlyConfigured` exception. - .. versionchanged:: 1.8 - - Previously, omitting this attribute was allowed and resulted in - a form with all fields of the model. - .. attribute:: success_url The URL to redirect to when the form is successfully processed. diff --git a/docs/ref/class-based-views/mixins-multiple-object.txt b/docs/ref/class-based-views/mixins-multiple-object.txt index 8d64604841e..6c4cdadedfa 100644 --- a/docs/ref/class-based-views/mixins-multiple-object.txt +++ b/docs/ref/class-based-views/mixins-multiple-object.txt @@ -74,8 +74,6 @@ MultipleObjectMixin .. attribute:: ordering - .. versionadded:: 1.8 - A string or list of strings specifying the ordering to apply to the ``queryset``. Valid values are the same as those for :meth:`~django.db.models.query.QuerySet.order_by`. @@ -120,8 +118,6 @@ MultipleObjectMixin .. method:: get_ordering() - .. versionadded:: 1.8 - Returns a string (or iterable of strings) that defines the ordering that will be applied to the ``queryset``. diff --git a/docs/ref/class-based-views/mixins-simple.txt b/docs/ref/class-based-views/mixins-simple.txt index ba18a1325ba..9550c22ed4b 100644 --- a/docs/ref/class-based-views/mixins-simple.txt +++ b/docs/ref/class-based-views/mixins-simple.txt @@ -51,8 +51,6 @@ TemplateResponseMixin .. attribute:: template_engine - .. versionadded:: 1.8 - The :setting:`NAME ` of a template engine to use for loading the template. ``template_engine`` is passed as the ``using`` keyword argument to ``response_class``. Default is ``None``, which @@ -61,25 +59,11 @@ TemplateResponseMixin .. attribute:: response_class The response class to be returned by ``render_to_response`` method. - Default is - :class:`TemplateResponse `. - The template and context of ``TemplateResponse`` instances can be - altered later (e.g. in + Default is :class:`TemplateResponse + `. The template and context + of ``TemplateResponse`` instances can be altered later (e.g. in :ref:`template response middleware `). - .. versionchanged:: 1.8 - - In older versions of Django, ``TemplateResponse`` used - :class:`~django.template.RequestContext` in such a way that values - from template context processors would override template variables - defined in your views. For example, if you subclassed - :class:`DetailView ` and - set ``context_object_name`` to ``user``, the - ``django.contrib.auth.context_processors.auth`` context processor - would overwrite your variable with the current user. Now, for - consistency with the ``render()`` shortcut, values in the context - provided by the class override values from context processors. - If you need custom template loading or custom context object instantiation, create a ``TemplateResponse`` subclass and assign it to ``response_class``. diff --git a/docs/ref/class-based-views/mixins-single-object.txt b/docs/ref/class-based-views/mixins-single-object.txt index 8296064c153..e7370b3ba85 100644 --- a/docs/ref/class-based-views/mixins-single-object.txt +++ b/docs/ref/class-based-views/mixins-single-object.txt @@ -53,8 +53,6 @@ SingleObjectMixin .. attribute:: query_pk_and_slug - .. versionadded:: 1.8 - If ``True``, causes :meth:`get_object()` to perform its lookup using both the primary key and the slug. Defaults to ``False``. @@ -81,10 +79,8 @@ SingleObjectMixin :attr:`slug_url_kwarg` argument, and performs a slug lookup using the :attr:`slug_field`. - .. versionchanged:: 1.8 - - When :attr:`query_pk_and_slug` is ``True``, ``get_object()`` will - perform its lookup using both the primary key and the slug. + When :attr:`query_pk_and_slug` is ``True``, ``get_object()`` will + perform its lookup using both the primary key and the slug. .. method:: get_queryset() diff --git a/docs/ref/contrib/admin/index.txt b/docs/ref/contrib/admin/index.txt index 321c6d83ad3..93af6e161bc 100644 --- a/docs/ref/contrib/admin/index.txt +++ b/docs/ref/contrib/admin/index.txt @@ -915,8 +915,6 @@ subclass:: ('is_staff', admin.BooleanFieldListFilter), ) - .. versionadded:: 1.8 - You can now limit the choices of a related model to the objects involved in that relation using ``RelatedOnlyFieldListFilter``:: @@ -1200,8 +1198,6 @@ subclass:: .. attribute:: ModelAdmin.show_full_result_count - .. versionadded:: 1.8 - Set ``show_full_result_count`` to control whether the full count of objects should be displayed on a filtered admin page (e.g. ``99 results (103 total)``). If this option is set to ``False``, a text like ``99 results (Show all)`` @@ -1711,8 +1707,6 @@ templates used by the :class:`ModelAdmin` views: .. method:: ModelAdmin.has_module_permission(request) - .. versionadded:: 1.8 - Should return ``True`` if displaying the module on the admin index page and accessing the module's index page is permitted, ``False`` otherwise. Uses :meth:`User.has_module_perms() @@ -1788,10 +1782,6 @@ templates used by the :class:`ModelAdmin` views: ``obj_id`` is the serialized identifier used to retrieve the object to be deleted. - .. versionadded:: 1.8 - - The ``obj_id`` parameter was added. - .. method:: ModelAdmin.get_changeform_initial_data(request) A hook for the initial data on admin change forms. By default, fields are @@ -1895,10 +1885,6 @@ To avoid conflicts with user-supplied scripts or libraries, Django's jQuery in your own admin JavaScript without including a second copy, you can use the ``django.jQuery`` object on changelist and add/edit views. -.. versionchanged:: 1.8 - - The embedded jQuery has been upgraded from 1.9.1 to 1.11.2. - .. versionchanged:: 1.9 The embedded jQuery has been upgraded from 1.11.2 to 2.1.4. This drops @@ -2119,8 +2105,6 @@ The ``InlineModelAdmin`` class adds: .. attribute:: InlineModelAdmin.show_change_link - .. versionadded:: 1.8 - Specifies whether or not inline objects that can be changed in the admin have a link to the change form. Defaults to ``False``. @@ -2519,8 +2503,6 @@ Templates can override or extend base admin templates as described in .. attribute:: AdminSite.site_url - .. versionadded:: 1.8 - The URL for the "View site" link at the top of each admin page. By default, ``site_url`` is ``/``. Set it to ``None`` to remove the link. @@ -2603,10 +2585,6 @@ Templates can override or extend base admin templates as described in * ``admin_url``: admin changelist URL for the model * ``add_url``: admin URL to add a new model instance - .. versionchanged:: 1.8 - - The ``request`` argument and the ``has_permission`` variable were added. - .. versionchanged:: 1.9 The ``available_apps`` variable was added. @@ -2732,12 +2710,6 @@ a pattern for your new view. ``AdminSite`` or ``self.admin_site.name`` if your view is on a ``ModelAdmin``. - .. versionchanged:: 1.8 - - In previous versions of Django, you had to provide the ``current_app`` - argument to :class:`~django.template.RequestContext` or - :class:`~django.template.Context` when rendering the template. - .. _auth_password_reset: Adding a password-reset feature diff --git a/docs/ref/contrib/auth.txt b/docs/ref/contrib/auth.txt index bf50e73d999..217bd432b5a 100644 --- a/docs/ref/contrib/auth.txt +++ b/docs/ref/contrib/auth.txt @@ -83,11 +83,6 @@ Fields A datetime of the user's last login. - .. versionchanged:: 1.8 - - This field will be ``null`` if the user has never logged in. - Previously it was set to the current date/time by default. - .. attribute:: date_joined A datetime designating when the account was created. Is set to the @@ -285,11 +280,6 @@ Anonymous users :meth:`~django.db.models.Model.save` and :meth:`~django.db.models.Model.delete()` raise :exc:`NotImplementedError`. - .. versionadded:: 1.8 - - ``AnonymousUser.get_username()`` has been added to - better mirror :class:`django.contrib.auth.models.User`. - In practice, you probably won't need to use :class:`~django.contrib.auth.models.AnonymousUser` objects on your own, but they're used by Web requests, as explained in the next section. @@ -311,10 +301,6 @@ fields: Required. 255 characters or fewer. Example: ``'Can vote'``. - .. versionchanged:: 1.8 - - The ``max_length`` increased from 50 to 255 characters. - .. attribute:: content_type Required. A reference to the ``django_content_type`` database table, @@ -460,8 +446,6 @@ The following backends are available in :mod:`django.contrib.auth.backends`: .. method:: get_user_permissions(user_obj, obj=None) - .. versionadded:: 1.8 - Returns the set of permission strings the ``user_obj`` has from their own user permissions. Returns an empty set if :meth:`~django.contrib.auth.models.AbstractBaseUser.is_anonymous` or diff --git a/docs/ref/contrib/flatpages.txt b/docs/ref/contrib/flatpages.txt index 0777a579f94..3326a93ea85 100644 --- a/docs/ref/contrib/flatpages.txt +++ b/docs/ref/contrib/flatpages.txt @@ -345,11 +345,6 @@ Integrating with :mod:`django.contrib.sitemaps` :attr:`~django.contrib.sitemaps.Sitemap.changefreq` or :attr:`~django.contrib.sitemaps.Sitemap.priority`. - .. versionchanged:: 1.8 - - This class is available from ``django.contrib.sitemaps.FlatPageSitemap`` - in older version of Django. - Example ------- diff --git a/docs/ref/contrib/gis/gdal.txt b/docs/ref/contrib/gis/gdal.txt index e04c69c8b4a..3aea16ad363 100644 --- a/docs/ref/contrib/gis/gdal.txt +++ b/docs/ref/contrib/gis/gdal.txt @@ -1090,8 +1090,6 @@ the same coordinate transformation repeatedly on different geometries:: Raster Data Objects =================== -.. versionadded:: 1.8 - ``GDALRaster`` ---------------- diff --git a/docs/ref/contrib/gis/install/postgis.txt b/docs/ref/contrib/gis/install/postgis.txt index 8e017933508..7e724938bac 100644 --- a/docs/ref/contrib/gis/install/postgis.txt +++ b/docs/ref/contrib/gis/install/postgis.txt @@ -64,7 +64,8 @@ spatial functionality:: > CREATE EXTENSION postgis; The database user must be a superuser in order to run -``CREATE EXTENSION postgis;``. +``CREATE EXTENSION postgis;``. The command is run during the :djadmin:`migrate` +process. GeoDjango does not currently leverage any `PostGIS topology functionality`__. If you plan to use those features at some point, you can also install the @@ -73,12 +74,6 @@ postgis_topology;``. __ http://postgis.net/docs/Topology.html -.. versionchanged:: 1.8 - - The ``CREATE EXTENSION postgis`` command is now automatically run during - the :djadmin:`migrate` process. You can still create it manually if you - wish. - Managing the database --------------------- diff --git a/docs/ref/contrib/gis/install/spatialite.txt b/docs/ref/contrib/gis/install/spatialite.txt index 01a9a266bc5..4ae99657155 100644 --- a/docs/ref/contrib/gis/install/spatialite.txt +++ b/docs/ref/contrib/gis/install/spatialite.txt @@ -160,8 +160,3 @@ Creating a spatial database for SpatiaLite When running ``manage.py migrate`` with a SQLite or SpatiaLite database, the database file will be automatically created if it doesn't exist. Django will also ensure that the spatial metadata are initialized in the database. - -.. versionchanged:: 1.8 - - Prior to Django 1.8, you had to initialize spatial metadata tables yourself - by manually running the "SELECT InitSpatialMetaData();" query. diff --git a/docs/ref/contrib/gis/serializers.txt b/docs/ref/contrib/gis/serializers.txt index 59266940e35..5226a9b9e8f 100644 --- a/docs/ref/contrib/gis/serializers.txt +++ b/docs/ref/contrib/gis/serializers.txt @@ -2,8 +2,6 @@ GeoJSON Serializer ================== -.. versionadded:: 1.8 - .. module:: django.contrib.gis.serializers.geojson :synopsis: Serialization of GeoDjango models in the GeoJSON format. diff --git a/docs/ref/contrib/postgres/index.txt b/docs/ref/contrib/postgres/index.txt index a1536680c7a..244fe123992 100644 --- a/docs/ref/contrib/postgres/index.txt +++ b/docs/ref/contrib/postgres/index.txt @@ -4,8 +4,6 @@ .. module:: django.contrib.postgres :synopsis: PostgreSQL-specific fields and features -.. versionadded:: 1.8 - PostgreSQL has a number of features which are not shared by the other databases Django supports. This optional module contains model fields and form fields for a number of PostgreSQL specific data types. diff --git a/docs/ref/contrib/sitemaps.txt b/docs/ref/contrib/sitemaps.txt index 004dffc76a2..a496522d56c 100644 --- a/docs/ref/contrib/sitemaps.txt +++ b/docs/ref/contrib/sitemaps.txt @@ -243,8 +243,6 @@ Sitemap class reference .. attribute:: Sitemap.i18n - .. versionadded:: 1.8 - **Optional.** A boolean attribute that defines if the URLs of this sitemap should diff --git a/docs/ref/contrib/sites.txt b/docs/ref/contrib/sites.txt index defa808207b..295bd868a74 100644 --- a/docs/ref/contrib/sites.txt +++ b/docs/ref/contrib/sites.txt @@ -509,10 +509,6 @@ Finally, to avoid repetitive fallback code, the framework provides a :class:`~django.contrib.sites.requests.RequestSite` which will always use the unmodified host. - .. versionchanged:: 1.8 - - Looking up the current site based on ``request.get_host()`` was added. - .. versionchanged:: 1.9 Retrying the lookup with the port stripped was added. diff --git a/docs/ref/databases.txt b/docs/ref/databases.txt index 2d866c5ae02..dec59915dc8 100644 --- a/docs/ref/databases.txt +++ b/docs/ref/databases.txt @@ -544,15 +544,6 @@ executing a command like:: or using a :class:`~django.db.migrations.operations.RunSQL` operation in a :ref:`data migration `. -.. versionchanged:: 1.8 - - Previously, Django truncated fractional seconds from ``datetime`` and - ``time`` values when using the MySQL backend. Now it lets the database - decide whether it should drop that part of the value or not. By default, new - ``DateTimeField`` or ``TimeField`` columns are now created with fractional - seconds support on MySQL 5.6.4 or later with either mysqlclient or - MySQLdb 1.2.5 or later. - ``TIMESTAMP`` columns ~~~~~~~~~~~~~~~~~~~~~ @@ -756,12 +747,6 @@ Some test suites also create views; to run these, the user also needs the CREATE VIEW WITH ADMIN OPTION privilege. In particular, this is needed for Django's own test suite. -.. versionchanged:: 1.8 - - Prior to Django 1.8, the test user was granted the CONNECT and RESOURCE - roles, so the extra privileges required for running the test suite were - different. - All of these privileges are included in the DBA role, which is appropriate for use on a private developer's database. diff --git a/docs/ref/django-admin.txt b/docs/ref/django-admin.txt index 41df95b37a4..a48a7043fda 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 [ []] .. 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 ` 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 ` 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']) diff --git a/docs/ref/exceptions.txt b/docs/ref/exceptions.txt index 46a0c81c22f..f847019c523 100644 --- a/docs/ref/exceptions.txt +++ b/docs/ref/exceptions.txt @@ -33,11 +33,6 @@ Django core exception classes are defined in ``django.core.exceptions``. ``_meta.get_field()`` method when the requested field does not exist on the model or on the model's parents. - .. versionchanged:: 1.8 - - This exception was previously defined only in - ``django.db.models.fields`` and wasn't part of the public API. - ``MultipleObjectsReturned`` --------------------------- @@ -250,8 +245,6 @@ Exceptions provided by the ``django.test`` package. .. exception:: client.RedirectCycleError - .. versionadded:: 1.8 - :exc:`~client.RedirectCycleError` is raised when the test client detects a loop or an overly long chain of redirects. diff --git a/docs/ref/files/file.txt b/docs/ref/files/file.txt index 14efb83fe6e..d6824af18c4 100644 --- a/docs/ref/files/file.txt +++ b/docs/ref/files/file.txt @@ -53,15 +53,6 @@ The ``File`` Class Iterate over the file yielding one line at a time. - .. versionchanged:: 1.8 - - ``File`` now uses `universal newlines`_. The following are - recognized as ending a line: the Unix end-of-line convention - ``'\n'``, the Windows convention ``'\r\n'``, and the old Macintosh - convention ``'\r'``. - - .. _universal newlines: https://www.python.org/dev/peps/pep-0278 - .. method:: chunks(chunk_size=None) Iterate over the file yielding "chunks" of a given size. ``chunk_size`` diff --git a/docs/ref/files/uploads.txt b/docs/ref/files/uploads.txt index 8bbdb161c3a..3304363b906 100644 --- a/docs/ref/files/uploads.txt +++ b/docs/ref/files/uploads.txt @@ -86,10 +86,6 @@ Here are some useful attributes of ``UploadedFile``: .. _universal newlines: https://www.python.org/dev/peps/pep-0278 - .. versionchanged:: 1.8 - - Previously lines were only split on the Unix end-of-line ``'\n'``. - Subclasses of ``UploadedFile`` include: .. class:: TemporaryUploadedFile diff --git a/docs/ref/forms/api.txt b/docs/ref/forms/api.txt index a8d2fa77ff2..c36f19ca2b7 100644 --- a/docs/ref/forms/api.txt +++ b/docs/ref/forms/api.txt @@ -185,8 +185,6 @@ Note that ``Form.add_error()`` automatically removes the relevant field from .. method:: Form.has_error(field, code=None) -.. versionadded:: 1.8 - This method returns a boolean designating whether a field has an error with a specific error ``code``. If ``code`` is ``None``, it will return ``True`` if the field contains any errors at all. @@ -570,11 +568,6 @@ classes, as needed. The HTML will look something like:: >>> f['subject'].label_tag(attrs={'class': 'foo'}) -.. versionchanged:: 1.8 - - The ``required_css_class`` will also be added to the ``