-
Notifications
You must be signed in to change notification settings - Fork 184
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
flask.ext.cache throws deprecation warnings #142
Comments
This starts from Flask |
I didn't saw the issue before, but just created a pull request for this #144 |
+1 for this issue. |
I created a pull request for this, however this pull is the best one I've seen out of the group to resolve this issue: |
Just wondering is this likely to be fix? |
Off what @bart3005 said, is anyone actively maintaining this package? Last commit was Sep 21, 2014. |
@deidyomega exactly what I was alluding to. |
yeah looking at the author's profile he's not using github for a year... is anyone planning on contacting him for a takeover of the package? |
+1 to make a release and upload package to pypi :-) |
I think this really needs taking over. I wonder if the owner would transfer? |
I reached out over email with a link to this thread. |
If anyone is interested, I forked this extension, merged a bunch of PRs and released it under a slightly different name (Flask-Caching). All the merged PRs can be found in the changelog: |
When using flask_cache:
ExtDeprecationWarning: Importing flask.ext.cache is deprecated, use flask_cache instead.
Even if user code is correct (using flask_cache instead of flask.ext.cache) the warning is still thrown. I suspect this is because internally an import to flask.ext.cache is called, thus spawning the warning.
The text was updated successfully, but these errors were encountered: