Hi All:
For convenience, The sheet of packages is attached
https://bugs.launchpad.net/starlingx/+bug/1808073 .
Thanks.
BR
Austin Sun.
From: Xie, Cindy
Sent: Tuesday, December 11, 2018 2:49 PM
To: 'Jolliffe, Ian' <Ian.Jolliffe@windriver.com>; Rowsell, Brent <Brent.Rowsell@windriver.com>; Wold, Saul <saul.wold@intel.com>; Sun, Austin <austin.sun@intel.com>; starlingx-discuss@lists.starlingx.io
Subject: Python2to3 status
Ian, Saul,
Per TSC request, here is the Python2to3 work items we are tracking and status:
1.
Repos for flocks with Python code (11 projects)
name |
Storyboards |
Status |
Notes |
Stx-config |
WIP |
|
|
Stx-distcloud |
Todo |
New |
|
Stx-distcloud-client |
Todo |
New |
|
Stx-fault |
Merged |
|
|
Stx-gui |
Merged |
|
|
Stx-ha |
Merged |
|
|
Stx-integ |
WIP |
|
|
Stx-metal |
Merged |
|
|
Stx-nfv |
WIP |
|
|
Stx-update |
Merged |
|
|
Stx-upstream |
Merged |
|
2.
For openStack repos: as we are moving to Stein, so the previous planned activities to backport those Python2to3 patches from master are no longer required. Checked with storage team, I am assuming other teams shall be in same situation.
3.
For other OS packages which are with Python code, detail readiness analysis posted here:
https://drive.google.com/open?id=1RT3oJJ5umHXZ_A--sJRpA23qB3LFY-lY. In short, we still found ~73 packages (out of 436) lacking of Python3 transition activities from upstream community.
This needs to further worked on and finalize the strategy.
We will discuss in Wed’s non-openstack distro weekly call if people still want details. @Austin, feel free to add anything.
Thx. - cindy