-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
werkzeug version in requirements.txt #4643
Comments
Are you sure you got this error with werkzeug 0.16.1? |
Yes it was 0.16.1. From pipdeptree: so... I installed flask-boto3, which pulled Flask 1.1.1, which than seeks for werkzeug.middleware module. After uprading werkzeug to 1.0.0 manage.py works, but pip complains about incompatibility; So yes. I figure it out and post requirements.txt, that will work for me. |
I figured it out. I think my biggest problem was insisting of using Redash without containers (I know that is now officially supported now) and it works. I installed it on a local VM and plan to rsync that to production server, to avoid installing a ton of dependencies for building Python modules and npm there. |
Since it's my first post here. Hi! :)
Issue Summary
I think, that werkzeug should have higher version in requirements.txt.
Steps to Reproduce
On werkzeug 0.16.1
python3 manage.py
Traceback (most recent call last):
File "manage.py", line 6, in
from redash.cli import manager
File "/home/lukasz/progi/redash/redash/redash/init.py", line 14, in
from .app import create_app # noqa
File "/home/lukasz/progi/redash/redash/redash/app.py", line 2, in
from werkzeug.middleware.proxy_fix import ProxyFix
ModuleNotFoundError: No module named 'werkzeug.middleware'
After uprading werkzeug to version 1.0.0:
python3 manage.py
Usage: manage.py [OPTIONS] COMMAND [ARGS]...
[...]
it works.
Technical details:
I think it's more do to with werkzeug as a Flask dependency, but I'm not sure.
From today.
None so far / Fedora 31
I pulled from git into virtualenv dir.
Thanks. Redash looks like a really good application.
The text was updated successfully, but these errors were encountered: