![](https://seccdn.libravatar.org/avatar/9880b3d4d617fb35fd01c59dbc92c1ca.jpg?s=120&d=mm&r=g)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Thu, 2017-06-29 at 00:20 +0200, Michael Ströder wrote:
Python 2 is not going to be around forever and for better or worse in some way or another the interests of openSUSE TW and openSUSE Leap are tied to SLE. SLE has a 10 year life cycle and having Python 2 as the default python interpreter in 2028 is not realistic. Thus at some point the switch needs to be made, which means things will be broken.
Still your text lacks any real reason for this change.
If in some time in the future openSUSE/SLES/whatever does not ship Python 2.x anymore then you can make this change.
At that point, making this change would _absolutely_ cause breakage and chaos. By introducing the change now, as a default behavior, anyone has an opportunity to "fall back" to python 2.7 in order to fix things that need fixing. If we wait until 2.x is dead, we've eliminated a great opportunity to preemptively fix problems. And realistically, all we're talking about is a small change in how update-alternatives is managed for `python`.
And of course everybody will agree that a missing Python 2.x will break things.
- -- James Mason Technical Architect, Public Cloud openSUSE Member SUSE jmason@suse.com -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEg/RjZ+RraZBnLRN4GzlRiGxEkCMFAllULlIACgkQGzlRiGxE kCN5GAgAqjG+3C4k/DWz9zvrtBNEwbPWLyjv/eO+UvLJPvIV1Bl3MWRtJpv8CdZN +nm0CaTfN5KIJynYj0ZJ0qDPZzKrBoMILJ0ZhV0SW4Has7Q1nCUdc2PXBFrD3NVF SheNfQn6eY6ZF+99ZJb+iuA5aUbGL3olxVBzZE4z63ykmlCdwWxKtGW11YP7kWoa tjQFSdnviiyNOdo67n0QHnhf/yaPyLBV7jsN9P9WBnz2Zi54+VdL/abMQu5bq0Q0 0iyTSYhpQ8qz48hwcP5YHgWn5KjHhIB8pC1cTqjk/Rc5BEVYrZu31EPB6iLov+62 VBw+imG1TFtQT2/J+5yubK2v4B16MA== =OR7p -----END PGP SIGNATURE-----