Mailinglist Archive: opensuse-factory (914 mails)

< Previous Next >
Re: [opensuse-factory] Switching default python to Python 3
Robert Schweikert wrote:
On 06/27/2017 05:06 AM, Michael Ströder wrote:
I'd vote against this breakage. Especially because it does not fix a real
problem. And
surely nobody is willing to maintain thousands of shee-bang patches.

Sorry, but "voting against" is not sufficient, you'll have to offer a
viable alternative solution, IMHO.

Well, rather *you* should provide a _strong_ reason why to make this change and
break things.

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. And of course everybody will agree that a
missing Python
2.x will break things.

Every developer who wants to prefer Python 3 will use a shee-bang with
/usr/bin/python3
anyway.

Now lets argue a bit about why it may be a good idea to do in TW what
SLE is planning to do.
- Lets say TW stays with Python 2 as the default interpreter, i.e. for
now we don't break anything. But SLE switches to Python 3 as the default
interpreter. Then when openSUSE Leap Next is released it will have the
default interpreter be Python 3. The result is that the distribution
that is being advertised as close to the cutting edge is using an older
interpreter than the distribution that is supposed to be somewhat behind
in the name of stability. Certainly that will create some kind of
perception problem.

IMO your simply overrating the term "default interpreter".

Ciao, Michael.

< Previous Next >
Follow Ups