The webservice command and related utilities are still being executed using Python 2. At least the dynamicproxy registration breaks with py3, didn't test more. This is a blocker for introducing Bullseye to parts of the infrastructure (bastions, grid (if not dead by that point), possibly worker docker containers).
Description
Description
Details
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Use Python 3 | operations/software/tools-webservice | master | +76 -59 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | taavi | T264713 Add Python 3.8/3.9 to Toolforge Kubernetes/Job Grid | |||
| Resolved | taavi | T266210 Add PHP 7.4 for Kubernetes | |||
| Resolved | taavi | T243159 Request to enable node version 12.14.1 in toolforge to deploy VideoCutTool | |||
| Resolved | taavi | T284590 Build Bullseye based Toolforge images | |||
| Invalid | None | T197804 Puppet: forbid new Python2 code | |||
| Resolved | taavi | T218427 Upgrade various Toolforge infrastructure scripts from Python 2 to Python 3 | |||
| Resolved | taavi | T284586 webservice: Use python 3 | |||
| Resolved | • Bstorm | T287421 Latest Toolforge docker images don't always have python2 installed at all |
Event Timeline
Comment Actions
Change 699482 had a related patch set uploaded (by Majavah; author: Majavah):
[operations/software/tools-webservice@master] Use Python 3
Comment Actions
Change 699482 merged by jenkins-bot:
[operations/software/tools-webservice@master] Use Python 3