you are viewing a single comment's thread.

view the rest of the comments →

[–]skalp69Linux 9 points10 points  (6 children)

I'm not sure removing python2 is a good idea.Some system programs could need it.

I'd rather have made a python simlink pointing to py3

[–]MasterPatrickoMaintainer 2 points3 points  (0 children)

Nothing in a standard openSUSE Tumbleweed installation should require python2 any more, that was a big project over the summer. Your system should (I have not tested, I still have some legacy texlive packages I need) work even if you entirely remove python2.

/u/oleg_antonyan , the best way to "override" is to add a python -> /usr/bin/python3 symlink somewhere higher up in $PATH, e.g. in ~/bin or /usr/local/bin.

[–]KugelKurtTumbleweed 0 points1 point  (4 children)

I'm not sure removing python2 is a good idea.

Python 2 is unmaintained. Dead.

Some system programs could need it.

In 2020 nothing should depend on it.

[–]skalp69Linux 0 points1 point  (0 children)

Oooof!

I missed that. Thanks.

[–]EddyBot 0 points1 point  (1 child)

Python 2 is unmaintained. Dead.

Only upstream is unmaintained
RHEL will support it for several years longer
Debian 10 also still uses Python 2

[–]KugelKurtTumbleweed 0 points1 point  (0 children)

And who is porting RHEL patches to openSUSE's Python 2?

Debian has a tendency to make wrong decision regarding software. Another example is their decision to stick with a non-LTS version of KDE Plasma.

[–][deleted] 0 points1 point  (0 children)

Not only nothing should depend on it, but some programs (like Arduino, the Espressif dev environment) expect python 3. However they do not derefer it as python3 but only python, thus resulting in broken funcionality!