Skip to content

community/py3-flask-caching: upgrade to 1.11.1

Simon Rupf requested to merge elrido/aports:flask-caching-1.11.1 into master

I need a little guidance on this one. AFAIK we only add new packages to community after they have proven to be maintained and working in testing. In this upgrade of the flask caching library they replaced/extracted some of their functionality with/into another library called cachelib, which is maintained by the same community. In order for the upgraded package to continue to work (without using pip), I would want to also add a packaged version of cachelib, so I can use the package dependencies to ensure the upgraded package will work out of the box.

The below merge request adds the new package and upgrades the other in separate commits, but both still in community. Should we instead add cachelib to testing and move py3-flask-caching back to testing as well?

Since I maintain py3-flask-caching (and use it in a project at work) I'm happy to maintain the new cachelib as well, regardless of which package groups they get moved to.

Version 1.11.1

Released 2022-05-27

  • Add cachelib to setup.py

Version 1.11.0

Released 2022-05-27

  • Add suport for cached/memoized generators. PR #286.
  • Add support for Flask 2.0 async. PR #282.
  • Cachelib is now used as backend. PR #308.
  • Drop support for python 3.6. PR #332.
  • Add support for dynamic cache timeouts #296.
  • Fix bug in CACHE_OPTIONS reading for redis in RedisSentinelCache. PR #343.

-- https://github.com/pallets-eco/flask-caching/blob/v1.11.1/CHANGES.rst

Merge request reports