amotl commented on issue #33162: URL: https://github.com/apache/superset/issues/33162#issuecomment-2971801834
Hi @mistercrunch. Thanks for outlining a workaround. However, it would be so sweet to keep the canonical `uv pip install apache-superset==4.*` on the CI workflow like it is implemented now. It is actually meant to be an integration test canary for both us (downstream towards CrateDB Nightly) and you (upstream towards stable releases of Apache Superset), that's why I am commenting here to relay the idea that both Apache Superset 3 and 4, when installing the package from PyPI without much ado, **is currently broken** due to misaligned runtime dependencies. In our humble opinion, this should be fixed. > Better use `pip install -r requirements/base.txt`? Thanks. Unfortunately, this is not an option, because we are trying to follow the idea that users solely use `uv pip install` as an interface to install packages, without obligatory access to the source repository. -- 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
