Deprecate werkzeug.contrib.cache

[lepture]

Werkzeug should definitely remove cache from itself. Werkzeug is designed for WSGI application. It seems cache has nothing to do with WSGI itself.

One certain decision in discussion Remove unnecessary crud from werkzeug.contrib would be removing cache. We could release next version with a deprecated warning, and remove it totally in version 1.0.

There are lots of issues to solve, we need to focus on the important things. We can't make a good cache library within werkzeug.

Any feedbacks? @pallets/devteam-werkzeug

[lepture]

I'm closing issues related to cache.

@pallets/devteam-werkzeug please re-open it if you find the issue to be very important.

[davidism]

We had an empty repository called werkzeug-cache that we created because someone wanted to work on it years ago. No commits were ever made, so I deleted it at the end of last year. You can recreate that if you want, we can come up with a more clever name later.

[davidism]

It would be good to reach out to the Flask-Caching maintainers to help support this.

[lepture]

Flask-Caching has ported werkzeug.contrib.cache:

https://github.com/sh4nks/flask-caching/tree/master/flask_caching/backends

[davidism]

I'm going to disable the caching tests for now, it's causing too much uncertainty with other PRs.

[davidism]

The tests have been disabled, and instantiating a cache class shows a deprecation warning, "Werkzeug cache is deprecated as of version 0.15 and will be removed in 1.0."