mirror of
https://github.com/Hopiu/django-cachalot.git
synced 2026-05-24 04:03:43 +00:00
Drop 1.8 and 1.10 from docs and setup.py
This commit is contained in:
parent
df42746729
commit
49cf92767c
4 changed files with 9 additions and 5 deletions
|
|
@ -1,6 +1,12 @@
|
|||
What’s new in django-cachalot?
|
||||
==============================
|
||||
|
||||
Unreleased
|
||||
----------
|
||||
|
||||
- Drops Django 1.8 support
|
||||
- Drops Django 1.10 support
|
||||
|
||||
1.5.0
|
||||
-----
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ Quick start
|
|||
Requirements
|
||||
............
|
||||
|
||||
- Django 1.8, 1.10 or 1.11
|
||||
- Django 1.11
|
||||
- Python 2.7, 3.4, 3.5 or 3.6
|
||||
- a cache configured as ``'default'`` with one of these backends:
|
||||
|
||||
|
|
@ -191,7 +191,7 @@ Examples:
|
|||
Template utils
|
||||
..............
|
||||
|
||||
`Caching template fragments <https://docs.djangoproject.com/en/1.8/topics/cache/#template-fragment-caching>`_
|
||||
`Caching template fragments <https://docs.djangoproject.com/en/1.11/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.
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
Django>=1.8
|
||||
Django>=1.11
|
||||
|
|
|
|||
2
setup.py
2
setup.py
|
|
@ -26,8 +26,6 @@ setup(
|
|||
'Intended Audience :: Developers',
|
||||
'License :: OSI Approved :: BSD License',
|
||||
'Operating System :: OS Independent',
|
||||
'Framework :: Django :: 1.8',
|
||||
'Framework :: Django :: 1.10',
|
||||
'Framework :: Django :: 1.11',
|
||||
'Programming Language :: Python :: 2',
|
||||
'Programming Language :: Python :: 2.7',
|
||||
|
|
|
|||
Loading…
Reference in a new issue