Todd Rme wrote: … While I appreciate that you're trying to accomodate all issues raised in this thread at the end your proposal still leads to /usr/bin/python pointing to python3.
But for me as a user, /usr/bin/python -> python3 is what I want. I also don’t understand the quoted recommendation that this shall be undesired. 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? Without „/usr/bin/python“ I see no change to continue this?! I like it, that python2 can run almost all python3 code. And I like the tool 2to3 which automatically converts almost all (of my) python2 code to run concurrently on 2 and 3. 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. By sticking /usr/bin/python to python2, the „brand“ /usr/bin/python is dead „forever“ once python2 disappears from the system due to EOL. 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. Fabian-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org