The problem is that in the Linux world there is no real, final, decision on what to do with the name "python". So, at least in Debian/Ubuntu, we have no plans on having /usr/bin/python to ever point to anything that is not Python 2. In Arch Linux, the situation is the opposite instead…
There is https://www.python.org/dev/peps/pep-0394/ that tried to reach a conclusion, but it actually caused even more confusion, so the world is all in flux. Having said that, if you explicitly write "python3" you are quite sure it will be run under python3, so it's generally a good idea, IMHO. If there really are shebangs or calls to python instead of python3, but the targets are compatible, then the distributions can patch those to python3 as needed without much trouble anyway, so, for now, we can consider this issue over. Later, in a few years, once the situation on the interpreter name stabilizes, this choice can be reviewed. -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to inkscape in Ubuntu. Matching subscriptions: Ubuntu Studio Bugs https://bugs.launchpad.net/bugs/1735363 Title: inkscape: Port to Python 3 Status in Inkscape: Fix Committed Status in inkscape package in Ubuntu: Confirmed Status in inkscape package in Debian: Confirmed Status in inkscape package in Fedora: Confirmed Bug description: inkscape: Use/Port of Python3 needed, or considering demotion. Currently seeded in usb (???), owned by desktop-packages. To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1735363/+subscriptions -- Mailing list: https://launchpad.net/~ubuntustudio-bugs Post to : ubuntustudio-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntustudio-bugs More help : https://help.launchpad.net/ListHelp