Comments (5)
I am closing this now as we don't depend on werkzeug.contrib.cache anymore. Yay! :)
from flask-caching.
For reference, here's the code for werkzeug.contrib.cache
: https://github.com/pallets/werkzeug/blob/master/werkzeug/contrib/cache.py
Flask-Caching relies on this module for the implementations of several of its caching backends:
from flask-caching.
@lepture is this the sort of approach you hand in mind: https://github.com/dchevell/flask-caching
I copied over the code from werkzeug.contrib.cache, replaced all imports in the core library and in tests, and updated the documentation to reference the internal implementations. Werkzeug origins are still clear.
All tests pass, and I tried the modded version in a project of mine that uses Flask-Caching and found no unexpected behaviours.
I'm not 100% confident in opening a PR without confirming whether this approach is the one you're looking for, or one that @sh4nks is happy with.
from flask-caching.
Yes, you can start with a copy of werkzeug.contrib.cache. But I do believe the cache module could be far more better than the one in werkzeug.
from flask-caching.
@dchevell that would be ok for now I think!
I actually had in mind to rewrite this extension to be a simple wrapper around dogpile.cache which would make maintaining this extension much easier. At the moment this is just an idea.. which lacks motivation and time :/
from flask-caching.
Related Issues (20)
- CACHE_OPTIONS has no effect if CACHE_REDIS_URL is set HOT 1
- Cache raised werkzeug HTTPExceptions HOT 1
- Memoize doesn't give correct results with list as one of the parameter in API HOT 6
- Redis cluster - read-replica routing
- Return type annotation for `get()` is too restrictive
- API documentation not rendering HOT 2
- Wrong output in conjunction with stream_template
- Using an integer in cache.get() doesn't give an appropriate error HOT 1
- RedisCache support for callable key prefixes was removed as of 1.11.0 HOT 1
- Caching a function with a DataFrame parameter doesn't work HOT 1
- _memver key entry for @cache.memoized call tracks TTL but probably shouldn't?
- Example code for checking value of memoized functions HOT 2
- Use cachelib version above 0.9.0 HOT 2
- key_prefix can support func ? : Expected type 'str', got '() -> str' instead HOT 3
- Please relax Flask version restriction to support `Flask==3.0.0` HOT 3
- Connect redis cluster with a redis url
- Documentation issues re: memoizing instance methods
- Documentation issue around memoize and identity?
- Respect `args_to_ignore` for keyword arguments when using `memoize`
- Invalid load key error due to reading .DS_store file on mac
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from flask-caching.