You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@shuchu I see the plan to drop Python 3.10 now that it's no longer maintained (#7101). Meanwhile, the 3.10 unit-test job fails on all PRs, because sqlglotc has no 3.10 wheels and the source build pulls an unpinned sqlglot that no longer compiles. #7104 fixes it by pinning build-time dependencies to the CI lock, and 3.10 passes there. It's harmless: the installed packages, the other Python versions and the existing setup all stay the same.
If dropping 3.10 is going to take longer, should we merge #7104 in the meantime to unblock CI?
Activity
patelchaitany commentedon Oct 27, 2026
Do we have a plan for Python 3.15 support? It was released on Oct 9, 2026, and adds lazy imports (PEP 810) and a stdlib profiler (PEP 799).
shuchu commentedon Nov 4, 2026
I don't have a concrete mind yet. let me dicuss with other maintainers.
patelchaitany commentedon Nov 4, 2026
@shuchu I see the plan to drop Python 3.10 now that it's no longer maintained (#7101). Meanwhile, the 3.10 unit-test job fails on all PRs, because
sqlglotchas no 3.10 wheels and the source build pulls an unpinnedsqlglotthat no longer compiles.#7104 fixes it by pinning build-time dependencies to the CI lock, and 3.10 passes there. It's harmless: the installed packages, the other Python versions and the existing setup all stay the same.
If dropping 3.10 is going to take longer, should we merge #7104 in the meantime to unblock CI?