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
/home/runner/work/errbot/errbot/.tox/py/lib/python3.12/site-packages/webob/compat.py:5: DeprecationWarning: 'cgi' is deprecated and slated forremovalin 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
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.
Activity
lbillinghamwrk commentedon Apr 23, 2025
If the webserver doesn't work, the fix may be to depend on
legacy-cgi; python_version >= '3.13'nzlosh commentedon Apr 23, 2025
Good spotting!
I've not seen anyone mention they're actively working on 3.13 support.
legacy-cgisuggests 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 commentedon Apr 25, 2025
Thank you. Do you think it could be worth adding
legacy-cgito 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 commentedon Apr 25, 2025
If
legacy-cgiget 3.13 support, it seems like a reasonable stopgap until we hit a hard blocker.sijis commentedon May 23, 2025
@lbillinghamwrk if you create a PR to add that dependency for 3.12, I'll merge that in.
Long term, as @nzlosh suggested, a switch to ASGI/WSGI may be the best approach.
fix(deps): allow webtest to work on python 3.13
lbillinghamwrk commentedon May 27, 2025
Thanks @sijis. I have opened #1729 to address this.
I've tested that
pip install .works on python 3.9 and 3.13.fix(deps): allow webtest to work on python 3.13
fix(deps): allow webtest to work on python 3.13 (#1729)
sijis commentedon May 1, 2026
merged to master.
fix(deps): allow webtest to work on python 3.13 (errbotio#1729)