-
Notifications
You must be signed in to change notification settings - Fork 14k
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
ModuleNotFoundError installing Superset 2.0.1 in a fresh virtual environment #22571
Comments
I just noticed that Superset 2.0.1's I have different ModuleNotFoundErrors every time I install a new version of Superset (I always file an issue here). In fact, looking at |
I am having the exact same issue: Python 3.8.16, Ubuntu 18.04 LTS
|
@alanorth try this snippet
|
@zhaoyongjie I ended up using this one liner shared in another issue. It installs the exact dependencies for Apache Superset 2.0.1, from its $ curl -sS https://raw.githubusercontent.com/apache/superset/2.0.1/requirements/base.txt | \
tail -n +10 | \
awk -v ORS=" " '/^[A-z]/{print}' | \
xargs pip install apache-superset==2.0.1 I still don't understand why pip installing |
this one liner worked for me too, thank you! |
Same problem Apply the solution of @zhaoyongjie, now i have :
|
Are you on the Superset 2.0.1? I can't reproduce it on the master and 2.0.1. |
Yes, I'm trying install Superset 2.0.1 on Rocky Linux 9.1 with Python 3.9 @zhaoyongjie, but i will try on Ubuntu 20.04 |
I got the same issue here, and this solution fixed it.
|
Thanks @XinbeiGong, it's worked ! I think it would be necessary to update the installation documentation, because it is a bit tedious to search all over the internet to install and operate this magnificent tool. Indirectly this repels a lot of potential users. |
Tagging @eschutho @eric-briscoe @AAfghahi as owners of 2.0.1 |
I was having this issue plus an issue with validate function: I think culprit was with WTForms, updating to 2.3.2 seems to have helped, looking at the change log they may have changed something in 2.3.1
|
Thanks for that info @jsanko9. It looks like we can pin WTForms to >=2.3.2 <3.0 and that should help with that issue. |
I just did a fresh install and got cryptography 39.0.0 (I can't help but notice that the dependencies that get installed by the process in |
I got the same error on Fedora 37. Just so you know I couldn't get it to work with Python default version on Fedora (3.11) since it's not compatible with lots of libraries and dependencies in Superset. In case anyone is interested I first had to build Python 3.8 from source:
This last line helps you leave your system-wide Python 3.11 intact. You can run python3.8 after that
After activating the new virtual environment and installing apache-superset with pip I got errors when I ran
as stated in the documentation (https://superset.apache.org/docs/installation/installing-superset-from-scratch/):
In order to fix this I had to run the lines @zhaoyongjie provided, which I reproduce below:
After that I ran
And I got the following errors:
@jsanko9 helped with this, I'm partly quoting the reply:
With that I could successfully run
|
@alanorth Hi, |
FWIW, there is a merged PR that removes the use of the private cryptography API |
Fixed installation, working on ubuntu 22.10
|
Can confirm, Ubuntu 20.04 py3.8 got stood up successfully with the following
|
您好,你发的邮件我已收到。
|
Closing because we realized that For better or worse, now I always install Superset using a one liner based on the example given earlier in this issue: $ curl -sS https://raw.githubusercontent.com/apache/superset/2.0.1/requirements/base.txt | \
tail -n +10 | \
awk -v ORS=" " '/^[A-z]/{print}' | \
xargs pip install apache-superset==2.0.1 |
Trying to install Superset 2.0.1 in a fresh Python 3.8.10 virtual environment fails with ModuleNotFoundError.
How to reproduce the bug
But clearly
cryptography
is installed:Expected results
Superset runs.
Actual results
ModuleNotFoundError from Python.
Environment
System is Ubuntu 20.04 "focal" with Python 3.8.10.
Checklist
Additional context
The system is currently running Superset 2.0.0 fine in another virtualenv.
The text was updated successfully, but these errors were encountered: