[Starlingx-discuss] Python2to3 status

Sun, Austin austin.sun at intel.com
Wed Dec 12 00:50:32 UTC 2018


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 at windriver.com>; Rowsell, Brent <Brent.Rowsell at windriver.com>; Wold, Saul <saul.wold at intel.com>; Sun, Austin <austin.sun at intel.com>; starlingx-discuss at 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

https://storyboard.openstack.org/#!/story/2003433

WIP



Stx-distcloud

https://storyboard.openstack.org/#!/story/2004585

Todo

New

Stx-distcloud-client

https://storyboard.openstack.org/#!/story/2004586

Todo

New

Stx-fault

https://storyboard.openstack.org/#!/story/2003310

Merged



Stx-gui

https://storyboard.openstack.org/#!/story/2003432

Merged



Stx-ha

https://storyboard.openstack.org/#!/story/2003430

Merged



Stx-integ

https://storyboard.openstack.org/#!/story/2002909

WIP



Stx-metal

https://storyboard.openstack.org/#!/story/2003426

Merged



Stx-nfv

https://storyboard.openstack.org/#!/story/2003427

WIP



Stx-update

https://storyboard.openstack.org/#!/story/2003429

Merged



Stx-upstream

https://storyboard.openstack.org/#!/story/2003428

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20181212/90b4a69c/attachment-0001.html>


More information about the Starlingx-discuss mailing list