Update Python version to 3.13

[yoshiokatsuneo]

What type of PR is this?

• Feature

Description

Update python version to 3.13, and packages needed to upgrade for it.

Before the PR, Redash supports python version 3.8 to 3.10. But, python 3.8 and 3.9 is already end of life, and 3.10 will be end of life in this October.

On the top of the efforts to update python version below, for now, I simply try to just update python and packages that needs to update to make updating easier.
At first, I tried to update to 3.14, but it was not so easy.

#7600
#7510

How is this tested?

• Unit tests (pytest, jest)
• E2E Tests (Cypress)
• Manually

Manual Testing

• make up (Starting Web service)
• create and run query
  • SQLite data source
  • PostgreSQL data source
  • MySQL data source
  • MongoDB data source
  • BigQuery data source
• Download as
  • CSV file
  • Excel file
• Login
  • Email
  • Google login

[cubic-dev-ai]

1 issue found across 5 files

Prompt for AI agents (all issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="pyproject.toml">

<violation number="1" location="pyproject.toml:90">
P2: `pyodbc` is declared twice — once in `[tool.poetry.dependencies]` and again in `[tool.poetry.group.all_ds.dependencies]`. This duplication requires keeping both entries in sync on every version bump (as happened here). The `all_ds` group entry should be removed since it's already declared in the main dependencies.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[cubic-dev-ai]

P2: pyodbc is declared twice — once in [tool.poetry.dependencies] and again in [tool.poetry.group.all_ds.dependencies]. This duplication requires keeping both entries in sync on every version bump (as happened here). The all_ds group entry should be removed since it's already declared in the main dependencies.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At pyproject.toml, line 90:

<comment>`pyodbc` is declared twice — once in `[tool.poetry.dependencies]` and again in `[tool.poetry.group.all_ds.dependencies]`. This duplication requires keeping both entries in sync on every version bump (as happened here). The `all_ds` group entry should be removed since it's already declared in the main dependencies.</comment>

<file context>
@@ -84,9 +85,9 @@ urllib3 = "1.26.19"
+xlsxwriter = "3.2.9"
 tzlocal = "4.3.1"
-pyodbc = "5.1.0"
+pyodbc = "5.3.0"
 debugpy = "^1.8.9"
 paramiko = "3.4.1"
</file context>

[eradman]

thank you for working on this @yoshiokatsuneo!

I'm seeing this warning from the manage command

$ docker compose exec server ./manage.py
/usr/local/lib/python3.13/site-packages/tdclient/user_api.py:18: SyntaxWarning: invalid escape sequence '\$'
  ``[!#\$%\-_=\+<>0-9a-zA-Z]``
[2026-02-23 13:43:09,143][PID:329][INFO][xmlschema] Include schema from 'file:///usr/local/lib/python3.13/site-packages/xmlschema/schemas/XSD_1.1/xsd11-extra.xsd'

[yoshiokatsuneo]

I'm seeing this warning from the manage command

$ docker compose exec server ./manage.py
/usr/local/lib/python3.13/site-packages/tdclient/user_api.py:18: SyntaxWarning: invalid escape sequence '\$'
  ``[!#\$%\-_=\+<>0-9a-zA-Z]``
[2026-02-23 13:43:09,143][PID:329][INFO][xmlschema] Include schema from 'file:///usr/local/lib/python3.13/site-packages/xmlschema/schemas/XSD_1.1/xsd11-extra.xsd'

@eradman

Thank you for the review !
I just fixed the warning by updating the td-client package from 1.0.0 to 1.5.0 .
(I could not easily update to the latest td-client 1.7.0, as it causes other dependency issue.)

bd27493

[eradman]

With Python 3.13 (and related modules) I had to raise memory limits in Kubernetes from 600 to 900M for the worker processes. I assume there is nothing we can do about this

[eradman]

Tested with PostgreSQL and Clickhouse data sources. So far no warnings, or failed jobs.

[yoshiokatsuneo]

@eradman Thank you for your review and testing !

[wtfiwtz]

Sorry I didn't get back to finish #7510
We did have one issue after deployment - orchestrated-io#18
If you'd like a PR for that, let me know.