8000 Status of Python 3.13 support · Issue #1721 · errbotio/errbot · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Status of Python 3.13 support #1721

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
lbillinghamwrk opened this issue Apr 23, 2025 · 4 comments
Open

Status of Python 3.13 support #1721

lbillinghamwrk opened this issue Apr 23, 2025 · 4 comments

Comments

@lbillinghamwrk
Copy link
lbillinghamwrk commented Apr 23, 2025 •
edited
Loading

Hello Folks,

Can you please help me understand the support status for the latest python?

It looks like we depend on cgi; apparently via webob and then via webtest which is used in production to validate incoming webhooks
However, cgi is no longer included in python 3.13.

While do have a test-suite running on 3.13 already python-package.yml; I'm not sure that we exercise the full webserving/webob path there.

The [latest PR checks run] (https://github.com/errbotio/errbot/actions/runs/14037314539/job/39298415722#step:5:256) does still show warnings about cgi

 /home/runner/work/errbot/errbot/.tox/py/lib/python3.12/site-packages/webob/compat.py:5: DeprecationWarning: 'cgi' is deprecated and slated for removal in Python 3.13
    from cgi import parse_header

Are we confident that CI exercises the cgi-ish code paths? Can we run fully on python 3.13
@lbillinghamwrk
Copy link
Author

If the webserver doesn't work, the fix may be to depend on legacy-cgi; python_version >= '3.13'

@nzlosh
Copy link
Contributor
nzlosh commented Apr 23, 2025

Good spotting!

I've not seen anyone mention they're actively working on 3.13 support. legacy-cgi suggests new projects use ASGI or WSGI. PEP-0594 states the cgi module is poorly designed and hard to maintain. The CGI architecture is also criticised as inefficient.

It seems to me that the best long term solution for the errbot project would be to migrate away from CGI to ASGI/WSGI, but this requires someone with the skills and time to volunteer and carry out the task to completion.

@lbillinghamwrk
Copy link
Author

Thank you. Do you think it could be worth adding legacy-cgi to our dependencies as a stopgap?

I can do that, or change things to flag max version is 3.12.

I wouldn't be capable of doing the refactor/migration in the foreseeable future.

@nzlosh
Copy link
Contributor
nzlosh commented Apr 25, 2025

If legacy-cgi get 3.13 support, it seems like a reasonable stopgap until we hit a hard blocker.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@nzlosh @lbillinghamwrk
0