GitHub user rusackas added a comment to the discussion: Roadmap to SQLAlchemy 2
Follow-up on the punch list above — two more items closed out: - #43496: verified the `ocient` driver's SQLAlchemy 2.0 compatibility, previously flagged "unverified" in #42542. Found and fixed a real (if narrow) bug along the way: `pyocient>=3.9.0` relocated its GIS classes from private top-level names to public ones under `pyocient.api`, which broke `test_ocient.py`'s fixtures. That breakage was invisible in standard CI since `pyocient` isn't a default test dependency — only surfaces if you actually install the `ocient` extra. All 21 tests pass now, confirming the driver itself is fine under 2.0. - #43497: removed `superset/utils/pandas_sqlalchemy_compat.py`, the shim that let pandas'\''s SQL IO tolerate a pre-2.0 SQLAlchemy install. Its own docstring called out removal once Superset requires SQLAlchemy >= 2, which is now the case. Remaining items are all upstream-blocked (aurora-data-api, d1, kusto, solr dialects with no 2.0 support on their end) — nothing actionable on Superset's side beyond tracking upstream. GitHub link: https://github.com/apache/superset/discussions/40273#discussioncomment-18141832 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
