configure.py assumes "python" command exists

Richard Kimberly Heck rikiheck at lyx.org
Mon Feb 15 04:27:40 UTC 2021


On 2/14/21 7:43 PM, Scott Kostyshak wrote:
> Some things did not work when I compiled on Ubuntu 20.10 because by
> default Ubuntu 20.10 does not have a "python" command and instead
> realies on "python2" and "python3" commands. The fix is easy: just
> needed to install the package "python-is-python3". I don't know much
> about this, but I think it is partly explained here:
>
> https://www.python.org/dev/peps/pep-0394/#recommendation
>
> LyX's configure.py assumes that the command "python" exists when setting
> the commands of some converters. Is this something we want to fix? Would
> it be reasonable for configure.py to just capture the path to the python
> command that it is called with and pass that on when it is setting the
> converter commands?
>
> Or for the next release cycle would it be reasonable to change all
> "python" commands to "python3" commands or is that not portable for all
> modern platforms (by the time the next major version is released)?

We have a Python detection routine, find_python_binary(), so it could be
modified to check for those commands explicitly. I'm reluctant to touch
that code myself though.

Riki




More information about the lyx-devel mailing list