On Fri, May 3, 2019 at 4:11 AM Tim Rühsen <[email protected]> wrote: > > On 5/2/19 6:12 PM, Jeffrey Walton wrote: > > On Thu, May 2, 2019 at 8:12 AM Darshit Shah <[email protected]> wrote: > >> ... > >> However, this _is_ a bug. Since if you see testenv/Makefile.am, we have a > >> `HAVE_PYTHON3` conditional block. And configure also checks for it. > > You are right, there is /usr/bin/python3.4 detected, so we have > > PYTHON=/usr/bin/python3.4 > > and HAVE_PYTHON3 being defined / true. > > So what about 'ln -s /usr/bin/python3.4 /usr/bin/python3' ? > > Meanwhile I check how we can make use of $PYTHON in the shebang line.
Here is some more information. I'm not a Python guy so I don't mess with it. It is in a default state from Oracle. $ command -v python3 $ $ ls /opt/csw/bin/py* /opt/csw/bin/pydoc /opt/csw/bin/python-config /opt/csw/bin/pydoc2 /opt/csw/bin/python2 /opt/csw/bin/pydoc2.6 /opt/csw/bin/python2-config /opt/csw/bin/python /opt/csw/bin/python2.6 $ ls /bin/py* /bin/pydoc /bin/python-config /bin/pydoc-2.6 /bin/python2.6 /bin/pydoc-2.7 /bin/python2.6-config /bin/pydoc3.4 /bin/python2.7 /bin/pygobject-codegen-2.0 /bin/python2.7-config /bin/pygobject27-codegen-2.0 /bin/python3.4 /bin/pygtk-codegen-2.0 /bin/python3.4-config /bin/pygtk27-codegen-2.0 /bin/python3.4m /bin/pyrexc /bin/python3.4m-config /bin/pyrexc2.6 /bin/pyvenv /bin/pyrexc2.7 /bin/pyvenv-3.4 /bin/python I think the takeaway is, use 'command -v python3' to test for the presence of Python. As far as I know it is POSIX and should work everywhere. I know another option is to try to configure Python. But I am not real happy with Python breaking basic I/O and I don't want to try to unfuck all the errors it could cause. I don't have enough experience to fix all of the errors. I'd rather leave it unconfigured. Jeff
