Flask-caching

Latest version: v2.3.0

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

Scan your dependencies

Page 5 of 8

1.1.0

Not secure
-------------

Released 2016-12-09

- Fix 'redis' backend import mechanisim. See `14`
- Made backends a module to better control which cache backends to expose
and moved our custom clients into a own module inside of the backends
module. See also `14` (and partly some own changes).
- Some docs and test changes. See `8`
and `12`

1.0.1

Not secure
-------------

Released 2016-08-30

- The caching wrappers like `add`, `set`, etc are now returning the wrapped
result as someone would expect. See `5`

1.0.0

Not secure
-------------

Released 2016-07-05

- Changed the way of importing Flask-Cache. Instead of using the depreacted
method for importing Flask Extensions (via ``flask.ext.cache``),
the name of the extension, ``flask_cache`` is used. Have a look at
`Flask's documentation`
for more information regarding this matter. This also fixes the
deprecation warning from Flask.
- Lots of PEP8 and Documentation fixes.
- Renamed this fork Flask-Caching (``flask_caching``) as it will now be
available on PyPI for download.

In addition to the above mentioned fixes, following pull requests have been
merged into this fork of `Flask-Cache`:

- `90 Update documentation: route decorator before cache`
- `95 Pass the memoize parameters into unless().`
- `109 wrapped function called twice`
- `117 Moves setting the app attribute to the _set_cache method`
- `121 fix doc for delete_memoized`
- `122 Added proxy for werkzeug get_dict`
- `123 "forced_update" option to 'cache' and 'memoize' decorators`
- `124 Fix handling utf8 key args` (cherry-picked)
- `125 Fix unittest failing for redis unittest`
- `127 Improve doc for using cached on view`
- `128 Doc for delete_memoized`
- `129 tries replacing inspect.getargspec with either signature or getfullargspec if possible`
- `make_cache_key() returning incorrect key` (cherry-picked)

0.13

------------

Released 2014-04-21

- Port to Python >= 3.3 (requiring Python 2.6/2.7 for 2.x).
- Fixed bug with using per-memoize timeouts greater than the default timeout
- Added better support for per-instance memoization.
- Various bug fixes

0.12

------------

Released 2013-04-29

- Changes jinja2 cache templates to use stable predictable keys. Previously
the key for a cache tag included the line number of the template, which made
it difficult to predict what the key would be outside of the application.
- Adds config variable `CACHE_NO_NULL_WARNING` to silence warning messages
when using 'null' cache as part of testing.
- Adds passthrough to clear entire cache backend.

0.11.1

--------------

Released 2013-04-7

- Bugfix for using memoize on instance methods.
The previous key was id(self), the new key is repr(self)

Page 5 of 8

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.