Switching to Python3 capable fork for suds
oslo.vmware would like to support 3.x but suds library is not
maintained and won't work under python 3. suds-jurko is the
most active fork of suds. Moving over projects will be a
step-by-step effort starting with oslo.vmware and then followed
by Nova and Cinder, once the CI jobs stabilize (both our CI and
MineSweeper), we should remove suds entirely from requirements.
We discussed this at the Design summit session for python3 and
there was consensus on this approach.
Blueprint information
- Status:
- Not started
- Approver:
- Doug Hellmann
- Priority:
- Undefined
- Drafter:
- Davanum Srinivas (DIMS)
- Direction:
- Approved
- Assignee:
- Davanum Srinivas (DIMS)
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Step 1: update oslo.vmware's python3 requirements txt to use suds-jurko. Make sure same code can run both against suds in python 27 and using suds-jurko with python3
Step 2: Investigate how to run MineSweeper (VMware CI) against suds-jurko for both python27 and python3
Step 3: Switch both oslo.vmware and nova to use suds-jurko for both python27 and python33
