Archlinux is doing this, and it's causing me problems.
I saw that the call to mentos.py is only done with the path to the file and relying on its shebang to call python. I think it could be not too hard to implement a way to configure pygments to specify a path to python and then using it to call mentos.py.
It would solve the problem for distros that now use /usr/bin/python for python3, without breaking backward compatibility.
PING. Come on, seriously. This is one hell of an annoying problem to leave for months on end. Can't you check to see if the /usr/bin/python2 executable exists in the filesystem and use that over /usr/bin/python?
Not sure how many distros are doing this now, but I know a few are using "python2" to indicate python 2.x nowadays - and some have set /usr/bin/python to mean python 3.x.
The text was updated successfully, but these errors were encountered: