Package: django-admin-caching
Django Admin Caching made easySetupConfiguring the adminRelease NotesContributingReporting issues/improvementsPull RequestsSetting up all Python versionsCode of ConductThe Django admin changelist rows are not contained within a block that could be
extended through standard template caching with tags. Also, the generation of the
cache key for more complex objects might be too complicated to do in the templates.
Plus there might be out-of-process changes (e.g.: one of manual data fixes) that
don’t change the cache key, but should invalidate the cached row.Hence the existence of this application - declaratively cache your admin rows!Setupinstall it viapip installdjango-admin-cachingadd it to your settings and it auto-registers itselfsettings.INSTALLED_APPS = [
   ...
   'django_admin_caching',
   ...
]configure the admins you want cached (see below for detail)Configuring the adminto enable cahcing, theadmin_caching_enabledattribute of the model’s
admin class must be set toTrue. Note this means you might need tounregisterthe default admin and register your custom one for third
party models (e.g.:django.contrib.auth.models.Group)the cache key by default is<admin class modulename>.<adminclass name>- <model class applabel>.<modelclassname>-<modelobject pk>. This could
be customized by adding a custom key method to the admin class that returns
the string key for the model object part of the key -def admin_caching_key(self, obj)ifsettings.USE_I18N(andsettings.USE_L10N) are enabled, for each
enabled setting, a prefix will be added to the above, e.g.:<languagename>.<localename>.<thekey from above>on the admin level, the cache’s name can be specified through theadmin_caching_cache_nameattribute. If omitted, it defaults todefaulton the admin level, the cache’s timeout  can be specified through theadmin_caching_timeout_secondsattribute. If omitted, it defaults to the
cache’sdefault_timeoutRelease Notes0.1.5 Update to supported versions.
* Drop support for Django 1.8, 1.9 and 1.10
* Drop support for Python 3.2 and 3.4
* Remove compatibility code0.1.5bugfix: AttributeError if all translation has been deactivated
-issue #100.1.4bugfix:setup.pyshould not roll back latest Django version
-issue #60.1.3add support for Django 1.11 (and thus for Python 3.6 too)0.1.2if i18n/l10n is enabled, account for it in the cache prefix0.1.1allow specifying the cache timeout on the admin class0.1.0 - initial releasesupports Django 1.8, 1.9, 1.10 on python 2.7, 3.3, 3.4, and 3.5supports the following configuration attributes on the admin classadmin_caching_enabledadmin_caching_cache_nameadmin_caching_keyfor custom object cache keyContributingAs an open source project, we welcome contributions.The code lives ongithub.Reporting issues/improvementsPlease open anissue on githubor provide apull requestwhether for code or for the documentation.For non-trivial changes, we kindly ask you to open an issue, as it might be rejected.
However, if the diff of a pull request better illustrates the point, feel free to make
it a pull request anyway.Pull Requestsfor code changesit must have tests covering the change. You might be asked to cover missing scenariosthe latestflake8will be run and shouldn’t produce any warningif the change is significant enough, documentation has to be providedSetting up all Python versionssudo apt-get -y install software-properties-common
sudo add-apt-repository ppa:fkrull/deadsnakes
sudo apt-get update
for version in 3.5 3.6; do
  py=python$version
  sudo apt-get -y install ${py} ${py}-dev
doneCode of ConductAs it is a Django extension, it followsDjango’s own Code of Conduct.
As there is no mailing list yet, please just email one of the main authors
(seesetup.pyfile orgithub contributors)