Django-cacheops

Latest version: v7.0.2

Safety actively analyzes 631178 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 5 of 10

3.1

Not secure
- added locking to combat dog-pile effect
- handle transactions smarter (ihucos)
- handle functions in cached_as() and cached() args
- do not allow unknown kwargs in cached_as()

3.0.1

Not secure
- support Django 1.10 (worked before, but now it's official)
- accept empty CACHEOPS_REDIS setting
- fixed ImportError in cleanfilecache command (Roman)

3.0

Not secure
- support PyPy
- support Python 3.5
- support Django 1.9
- added transparent transaction handling (Joel Hillacre)
- added .invalidated_update()
- added cache_read signal (Joona Pääkkönen)
- added CACHEOPS_ENABLED setting
- invalidate on intermediate tables in long joins
- support settings override
- made CACHEOPS keys case insensitive
- allow redis connection settings to be specified by a URL (Tim Savage)
- fixed router support
- fixed clone cache settings affecting original queryset
- more fixes for non-ascii in str params
- calc func cache keys smarter
- no_invalidation optimizations
Backwards incompatible changes:
- Django 1.6 and earlier no longer supported
- dropped old CACHEOPS setting format
- removed CACHEOPS_FAKE setting
- removed .cached_call() from basic and file caches
- disabled cacheops for fake migration models

2.4.5

Not secure
- backport: disabled cacheops for fake migration models
- disabled cacheops for south models
- fixed get_queryset() on custom qs rename bug

2.4.3

Not secure
- fixed .get() on reverse fk related manager
- fixed memory leak on migrations

2.4.2

Not secure
- fixed .values() and .values_list() in Django 1.9
- stopped sharing cache between proxies and base

Page 5 of 10

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.