Fabian Wein wrote:
But for me as a user, /usr/bin/python -> python3 is what I want.
Why? Which issue do you want to solve? Just typing "python" instead of "python3"?
What is the point of writing python code compatible with python2 and python3 to run on new machines with insufficient python2 support (als TW) and old machines w/o python3 concurrently then?
How do you know that Python code with shee-bang /usr/bin/python is compatible to Python 2.x and 3.x? If it's not fully compatible how do you avoid damage to your system, security issues etc.?
If there is code, which cannot or does not wanted to be upgraded one simply has to replace /usr/bin/python by /usr/bin/python2 and wait up to the time no python2 is available any more and one finally is forced to upgrade the code.
*Who* is going to change the shee-bang to /usr/bin/python2 if the upstream developers uses /usr/bin/python assuming that Python 2 will implicitly be used? *Who* is going to maintain all the necessary patches?
By sticking /usr/bin/python to python2, the „brand“ /usr/bin/python is dead „forever“
Yes. So what?
Indeed I currently let point /usr/bin/python -> python3 and the only issue I have is, that the textext plugin and eps importer from inkscape does not work.
But why do you assume your personal experience to be relevant at all for all the other deployments using Python? Ciao, Michael.