← Back to team overview

cloud-init team mailing list archive

cloud-init removal of python 2.6 support, and python 2 deprecation plan

 

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi all,

Last week at the cloud-init summit we discussed the different python
versions that cloud-init supports.

Bullet point outcome of that is:
 * cloud-init release 18.4 (due 2018-09-20) will be the last release
   supporting python 2.6
 * cloud-init will drop all python 2 support from upstream in June of 2020.
 * cloud-init supports Python 3 version 3.5+

For more details, read on below.

## cloud-init Python 2.6 and Python 2 Deprecation ##
In cloud-init releases up to 18.3 and current master, support running in
Python back to version 2.6 and includes non-standardlib libraries back to
the versions shipped in CentOS 6/EPEL.

Upstream has carried Python 2.6 for CentOS 6 support only. No other
supported platform ships a Python 2.6 interpreter. Supporting Python 2.6
has costs to upstream primarily in developer velocity and in resources for
continuous integration.

18.4 (due 2018-09-20) will be the last release with 2.6 support.

After the release of 18.4 upstream code cleanups and targeted branches
will be accepted that removes python2.6 code.  Continuous integration
will no longer run against python 2.6.

## Python 2.7 support ##
cloud-init will drop support Python 2.7 in June of 2020.

As part of thinking about dropping support for Python 2.6, we have also
discussed the future inevitable drop of Python 2 entirely.

The June 2020 date is in line with the end of life for Python 2.7 from
Python upstream, which currently says " there will be bugfix releases
until 2020."

## Python 3 versions. ##
cloud-init supports Python 3 version 3.5+

If you have a platform that needs support and supports python 3 at version
less than 3.5, please respond here.

Thanks,
Scott
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEW2EmXixPNE1DHc/pHkQQpAJLxvAFAluFdiIACgkQHkQQpAJL
xvCZ2A//ZBlznmFYzKDKIrBPxfW+0q7i7C4ra5v4NQHms8cEcygratXNOo8iDKu8
dQ4zqnK0RpMdd+lkfaK5owi9y+H2dtKxb3jlYsxbED25MxDHgaRO5DUghg9bkWqA
sU5mgvU2R1obif3vAJhCfbEYvKYpdCSGfgpyNbPxtdW4lcWw/HQ3E478o4/9LObD
+dguj3TR3bhAavZyTh+WKeccgpDpVYM4SFTwuqhsylqtr7jbSi0wWv8zj4bLdaRP
uvJZCmPAQvrE4uZ5l/aMaZfHjFCH1NvNo3ZQiQ6YDKzg1IWF9Zbj7smUnu736VxP
YF/MmP9K6D0gbsKW+ZK59WpnsaipXWbA9eeQwIDv9rttEJDQDiMvbvaUVUwrovix
ghyTu8u4LSbijsRzcENVOYQQMh6/sNKoImur/bAMsnKE9RDnc9f9vogg0m16rVYP
VSsmmO+Lfm0Bu29F8txpUHdoqU8eH4Z70KFGlgIAeWhkI2LM6S3tUXQW0aZQB1nY
sFhf9yWM3hrarsowAKUXajgP6gJ19RZUEw6xy/1cefCM9Ex8GxvRoHKgArYM/WFf
IMT9xmVMzBzLZZvoC77UvUbN4IRpXKfnLdDTRPOsiOhqvNmIKyxjJOBTLL5vMVae
2EWXzZWjW2Pp8eJy0Vjil6KcWwUUpzKEhxcl23Xyc3hAKfEQiBQ=
=OPqT
-----END PGP SIGNATURE-----


Follow ups