Designate stable/wallaby install fails: suds-jurko use_2to3 is invalid

When installing designate stable/wallaby downstream with more modern dependencies, the install fails with: error in suds-jurko setup command: use_2to3 is invalid

2022-09-24 13:17:50.503711 | container | Collecting suds-jurko>=0.6
2022-09-24 13:17:50.516858 | container | Downloading suds-jurko-0.6.zip (255 kB)
2022-09-24 13:17:50.529055 | container | ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 255.8/255.8 KB 24.9 MB/s eta 0:00:00
2022-09-24 13:17:50.547561 | container | Preparing metadata (setup.py): started
2022-09-24 13:17:51.357323 | container | Preparing metadata (setup.py): finished with status 'error'
2022-09-24 13:17:51.362618 | container | error: subprocess-exited-with-error
2022-09-24 13:17:51.362648 | container |
2022-09-24 13:17:51.362658 | container | × python setup.py egg_info did not run successfully.
2022-09-24 13:17:51.362684 | container | │ exit code: 1
2022-09-24 13:17:51.362694 | container | ╰─> [1 lines of output]
2022-09-24 13:17:51.362700 | container | error in suds-jurko setup command: use_2to3 is invalid.
2022-09-24 13:17:51.362708 | container | [end of output]
2022-09-24 13:17:51.362715 | container |
2022-09-24 13:17:51.362724 | container | note: This error originates from a subprocess, and is likely not a problem with pip.
2022-09-24 13:17:51.364608 | container | error: metadata-generation-failed
2022-09-24 13:17:51.364621 | container |
2022-09-24 13:17:51.364627 | container | × Encountered error while generating package metadata.
2022-09-24 13:17:51.364633 | container | ╰─> See above for output.
2022-09-24 13:17:51.364638 | container |
2022-09-24 13:17:51.3642022-09-24 13:17:50.503711 | container | Collecting suds-jurko>=0.6
2022-09-24 13:17:50.516858 | container | Downloading suds-jurko-0.6.zip (255 kB)
2022-09-24 13:17:50.529055 | container | ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 255.8/255.8 KB 24.9 MB/s eta 0:00:00
2022-09-24 13:17:50.547561 | container | Preparing metadata (setup.py): started
2022-09-24 13:17:51.357323 | container | Preparing metadata (setup.py): finished with status 'error'
2022-09-24 13:17:51.362618 | container | error: subprocess-exited-with-error
2022-09-24 13:17:51.362648 | container |
2022-09-24 13:17:51.362658 | container | × python setup.py egg_info did not run successfully.
2022-09-24 13:17:51.362684 | container | │ exit code: 1
2022-09-24 13:17:51.362694 | container | ╰─> [1 lines of output]
2022-09-24 13:17:51.362700 | container | error in suds-jurko setup command: use_2to3 is invalid.
2022-09-24 13:17:51.362708 | container | [end of output]
2022-09-24 13:17:51.362715 | container |
2022-09-24 13:17:51.362724 | container | note: This error originates from a subprocess, and is likely not a problem with pip.
2022-09-24 13:17:51.364608 | container | error: metadata-generation-failed
2022-09-24 13:17:51.364621 | container |
2022-09-24 13:17:51.364627 | container | × Encountered error while generating package metadata.
2022-09-24 13:17:51.364633 | container | ╰─> See above for output.
2022-09-24 13:17:51.364638 | container |
2022-09-24 13:17:51.364644 | container | note: This is an issue with the package mentioned above, not pip.
2022-09-24 13:17:51.364650 | container | hint: See above for details.
2022-09-24 13:17:51.368653 | container | WARNING: You are using pip version 22.0.4; however, version 22.2.2 is available.
2022-09-24 13:17:51.368663 | container | You should consider upgrading via the '/root/src/code.engineering.redhat.com/openstack-designate/.tox/pep8/bin/python -m pip install --upgrade pip' command.
2022-09-24 13:17:51.538175 | container | ERROR: invocation failed (exit code 1)
2022-09-24 13:17:51.538287 | container | pep8 finish: developpkg /root/src/code.engineering.redhat.com/openstack-designate after 7.73 seconds
2022-09-24 13:17:51.538478 | container | ___________________________________ summary ____________________________________
2022-09-24 13:17:51.538695 | container | ERROR: pep8: InvocationError for command /root/src/code.engineering.redhat.com/openstack-designate/.tox/pep8/bin/pip install --exists-action w -e . (exited with code 1)
2022-09-24 13:17:51.935631 | container | ERROR
2022-09-24 13:17:51.935807 | container | {
2022-09-24 13:17:51.935838 | container | "delta": "0:00:40.784034",
2022-09-24 13:17:51.935861 | container | "end": "2022-09-24 13:17:51.573975",
2022-09-24 13:17:51.935882 | container | "msg": "non-zero return code",
2022-09-24 13:17:51.935901 | container | "rc": 1,
2022-09-24 13:17:51.935920 | container | "start": "2022-09-24 13:17:10.789941"
2022-09-24 13:17:51.935940 | container | }
```644 | container | note: This is an issue with the package mentioned above, not pip.
2022-09-24 13:17:51.364650 | container | hint: See above for details.
2022-09-24 13:17:51.368653 | container | WARNING: You are using pip version 22.0.4; however, version 22.2.2 is available.
2022-09-24 13:17:51.368663 | container | You should consider upgrading via the '/root/src/code.engineering.redhat.com/openstack-designate/.tox/pep8/bin/python -m pip install --upgrade pip' command.
2022-09-24 13:17:51.538175 | container | ERROR: invocation failed (exit code 1)
2022-09-24 13:17:51.538287 | container | pep8 finish: developpkg /root/src/code.engineering.redhat.com/openstack-designate after 7.73 seconds
2022-09-24 13:17:51.538478 | container | ___________________________________ summary ____________________________________
2022-09-24 13:17:51.538695 | container | ERROR: pep8: InvocationError for command /root/src/code.engineering.redhat.com/openstack-designate/.tox/pep8/bin/pip install --exists-action w -e . (exited with code 1)
2022-09-24 13:17:51.935631 | container | ERROR
2022-09-24 13:17:51.935807 | container | {
2022-09-24 13:17:51.935838 | container | "delta": "0:00:40.784034",
2022-09-24 13:17:51.935861 | container | "end": "2022-09-24 13:17:51.573975",
2022-09-24 13:17:51.935882 | container | "msg": "non-zero return code",
2022-09-24 13:17:51.935901 | container | "rc": 1,
2022-09-24 13:17:51.935920 | container | "start": "2022-09-24 13:17:10.789941"
2022-09-24 13:17:51.935940 | container | }