Re: python 3 vs 2
Thank you Tony. Let’s address this point today during SECCOM meeting.
ONAP SECCOM Chair
Leader in IT & Network Convergent Operations
Orange Polska S.A.
Corporate Services Agency
Obrzeżna 7, 02-691 Warszawa
From: ZWARICO, AMY [mailto:az9121@...]
Sent: Monday, May 6, 2019 10:53 PM
To: HANSEN, TONY L; onap-seccom@...
Cc: Pawlak Paweł 3 - Korpo
Subject: RE: python 3 vs 2
From: HANSEN, TONY L
Next January, Python 2 loses all support from python.org. They’ve already extended their support for 2.x by 5 years. This means that come January 1, 2020, there will no longer be a supported version of python 2.
From https://www.python.org/dev/peps/pep-0373/ we find this:
The End Of Life date (EOL, sunset date) for Python 2.7 has been moved five years into the future, to 2020 [n.b. from 2015]. This decision was made to clarify the status of Python 2.7 and relieve worries for those users who cannot yet migrate to Python 3. See also PEP 466.
Being the last of the 2.x series, 2.7 will have an extended period of maintenance. Specifically, 2.7 will receive bugfix support until January 1, 2020. After the last release, 2.7 will receive no support.
Shortly after El Alto is frozen, any code in ONAP that still uses Python 2.7 will no longer be based on a supported FLOSS language.
From a Seccom point of view, this means that there will be no more security fixes from python.org for python 2.7.
I think it would be worth issuing a SECCOM statement about Python 2.7, possibly as part of El Alto requirements.