alanorth commented on issue #22571: URL: https://github.com/apache/superset/issues/22571#issuecomment-1369974412
I just noticed that [Superset 2.0.1's `requirements/base.txt`](https://github.com/apache/superset/blob/2.0.1/requirements/base.txt#L69) says it wants cryptography==3.4.7. If I install that manually then superset runs as expected. I have different ModuleNotFoundErrors every time I install a new version of Superset (I always file an issue here). In fact, looking at `pip list` in my virtual environment, I see several other packages that are the wrong version. What is going on with the Python packaging of the pip version that causes `pip install apache-superset==2.0.1` to not install the exact version dependencies? Why do the Superset docs still recommend using the pip install method at all? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org
