Dogpile.cache

Latest version: v1.3.3

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

Scan your dependencies

Page 5 of 9

0.7.0

Released: Mon Dec 10 2018
- **[bug]** The `decorator` module is now used when creating function decorators
within `CacheRegion.cache_on_arguments()` and
`CacheRegion.cache_multi_on_arguments()` so that function signatures
are preserved. Pull request courtesy ankitpatel96.

Additionally adds a small performance enhancement which is to avoid
internally creating a `wraps()` decorator for the creator function on
every get operation, by allowing the arguments to the creator be passed
separately to `CacheRegion.get_or_create()`.

References: [137](ticket:137)

- **[bug] [py3k]** Fixed all Python 3.x deprecation warnings including
`inspect.getargspec()`.

References: [129](ticket:129)


rel_0_6_8

0.6.8

Released: Sat Nov 24 2018
- **[change]** Project hosting has moved to GitHub, under the SQLAlchemy
organization at [https://github.com/sqlalchemy/dogpile.cache](https://github.com/sqlalchemy/dogpile.cache)


rel_0_6_7

0.6.7

Released: Thu Jul 26 2018
- **[bug]** Fixed issue in the `CacheRegion.get_or_create_multi()` method which
was erroneously considering the cached value as the timestamp field if the
`CacheRegion.invalidate()` method had ben used, usually causing a
`TypeError` to occur, or in less frequent cases an invalid result for
whether or not the cached value was invalid, leading to excessive caching
or regeneration. The issue was a regression caused by an implementation
issue in the pluggable invalidation feature added in [38](ticket:38).

References: [128](ticket:128)


rel_0_6_6

0.6.6

Released: Wed Jun 27 2018
- **[feature]** Added method `CacheRegion.actual_backend` which calculates and
caches the actual backend for the region, which may be abstracted by
the use of one or more `ProxyBackend` subclasses.

References: [123](ticket:123)

- **[bug]** Fixed a condition in the `Lock` where the "get" function could be
called a second time unnecessarily, when returning an existing, expired
value from the cache.

References: [122](ticket:122)


rel_0_6_5

0.6.5

Released: Mon Mar 5 2018
- **[bug]** Fixed import issue for Python 3.7 where several variables named "async"
were, leading to syntax errors. Pull request courtesy Brian Sheldon.

References: [119](ticket:119)


rel_0_6_4

0.6.4

Released: Mon Jun 26, 2017
- **[bug]** The method `Region.get_or_create_multi()` will not pass to the
cache backend if no values are ultimately to be stored, based on
the use of the `Region.get_or_create_multi.should_cache_fn`
function. This empty dictionary is unnecessary and can cause API
problems for backends like that of Redis. Pull request courtesy
Tobias Sauerwein.

- **[bug]** The `api.NO_VALUE` constant now has a fixed `__repr__()`
output, so that scenarios where this constant's string value
ends up being used as a cache key do not create multiple values.
Pull request courtesy Paul Brown.

- **[bug]** A new exception class `exception.PluginNotFound` is now
raised when a particular cache plugin class cannot be located
either as a setuptools entrypoint or as a registered backend.
Previously, a plain `Exception` was thrown. Pull request
courtesy Jamie Lennox.


rel_0_6_3

Page 5 of 9

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.