sadpandajoe commented on code in PR #43502:
URL: https://github.com/apache/superset/pull/43502#discussion_r3940658585
##########
pyproject.toml:
##########
@@ -271,18 +275,34 @@ tdengine = [
"taos-ws-py>=0.7.0"
]
teradata = ["teradatasql>=20.0.0.66"]
+# TimescaleDB is a genuine Postgres extension, not a fork - connects via the
+# plain postgresql dialect, same driver as postgres.
+timescaledb = ["apache-superset[postgres]"]
thumbnails = [] # deprecated, will be removed in 7.0
vertica = ["sqlalchemy-vertica-python>= 0.6.3, < 0.7"]
netezza = ["nzalchemy>= 11.1.2, < 11.2"]
starrocks = ["starrocks>=1.3.4, <2"]
doris = ["pydoris>=1.2.0, <2.0.0"]
+# oceanbase_py pins sqlalchemy-utils>=0.38.3,<0.39, which conflicts outright
+# with Superset's own sqlalchemy-utils==0.42.1 pin -- `pip install
+# apache-superset[oceanbase]` cannot resolve. CI installs oceanbase_py as a
+# standalone package with --no-deps instead (see testcontainers.yml); this
+# extra is kept only as a documented, deliberately unusable install path
Review Comment:
Keeping this in the published extra list means `pip install
apache-superset[oceanbase]` still asks pip to solve the incompatible
constraints; this source comment is not surfaced to installers, so they get a
resolution failure rather than an unsupported-feature indication. Could this
remove the extra or make its constraints resolvable instead of retaining an
intentionally unusable install command?
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
