Further Django 2.0 missing references.

This commit is contained in:
Bertrand Bordage 2018-05-04 20:49:56 +02:00
parent 74e000b8e2
commit 8bb1ca1753
3 changed files with 9 additions and 8 deletions

View file

@ -4,15 +4,15 @@ Quick start
Requirements
............
- Django 1.11
- Django 1.11 or 2.0
- Python 2.7, 3.4, 3.5 or 3.6
- a cache configured as ``'default'`` with one of these backends:
- `django-redis <https://github.com/niwinz/django-redis>`_
- `memcached <https://docs.djangoproject.com/en/1.11/topics/cache/#memcached>`_
- `memcached <https://docs.djangoproject.com/en/2.0/topics/cache/#memcached>`_
(using either python-memcached or pylibmc)
- `filebased <https://docs.djangoproject.com/en/1.11/topics/cache/#filesystem-caching>`_
- `locmem <https://docs.djangoproject.com/en/1.11/topics/cache/#local-memory-caching>`_
- `filebased <https://docs.djangoproject.com/en/2.0/topics/cache/#filesystem-caching>`_
- `locmem <https://docs.djangoproject.com/en/2.0/topics/cache/#local-memory-caching>`_
(but its not shared between processes, see :ref:`locmem limits <Locmem>`)
- one of these databases:
@ -67,7 +67,7 @@ Settings
change this setting, you end up on a cache that may contain stale data.
.. |CACHES| replace:: ``CACHES``
.. _CACHES: https://docs.djangoproject.com/en/1.11/ref/settings/#std:setting-CACHES
.. _CACHES: https://docs.djangoproject.com/en/2.0/ref/settings/#std:setting-CACHES
``CACHALOT_DATABASES``
~~~~~~~~~~~~~~~~~~~~~~
@ -80,7 +80,7 @@ Settings
engines.
.. |DATABASES| replace:: ``DATABASES``
.. _DATABASES: https://docs.djangoproject.com/en/1.11/ref/settings/#std:setting-DATABASES
.. _DATABASES: https://docs.djangoproject.com/en/2.0/ref/settings/#std:setting-DATABASES
``CACHALOT_TIMEOUT``
~~~~~~~~~~~~~~~~~~~~
@ -191,7 +191,7 @@ Examples:
Template utils
..............
`Caching template fragments <https://docs.djangoproject.com/en/1.11/topics/cache/#template-fragment-caching>`_
`Caching template fragments <https://docs.djangoproject.com/en/2.0/topics/cache/#template-fragment-caching>`_
can be extremely powerful to speedup a Django application. However, it often
means you have to adapt your models to get a relevant cache key, typically
by adding a timestamp that refers to the last modification of the object.

View file

@ -1 +1 @@
Django>=1.11
Django>=1.11,<2.1

View file

@ -27,6 +27,7 @@ setup(
'License :: OSI Approved :: BSD License',
'Operating System :: OS Independent',
'Framework :: Django :: 1.11',
'Framework :: Django :: 2.0',
'Programming Language :: Python :: 2',
'Programming Language :: Python :: 2.7',
'Programming Language :: Python :: 3',