[
https://issues.apache.org/jira/browse/PROTON-2217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Daněk updated PROTON-2217:
-------------------------------
Description:
I have the same experience that was reported elsewhere:
bq. For me, the find_package(PythonInterp) call was always finding the older
interpreter (2.7) even though everything pointed to the newer one (3.6). (from
https://reviews.llvm.org/D64881)
This behavior is unfortunate on Ubuntu 20.04 Focal, where both python2 and
python3 are available, but pip for python2 is not packaged. Therefore it makes
sense to build proton with python3; which would make sense anyways, since
Python 2.7 is deprecated by the Python Software Foundation nowadays..
Besides removing python2 as discussed on the linked page, there is currently
nicer way to force python3 that worked for me, by setting
{{-DPYTHON_EXECUTABLE=/usr/bin/python3}} CMake variable.
Related dispatch issue, DISPATCH-187
was:
I have the same experience that was reported elsewhere:
bq. For me, the find_package(PythonInterp) call was always finding the older
interpreter (2.7) even though everything pointed to the newer one (3.6). (from
https://reviews.llvm.org/D64881)
This behavior is unfortunate on Ubuntu 20.04 Focal, where both python2 and
python3 are available, but pip for python2 is not packaged. Therefore it makes
sense to build proton with python3; which would make sense anyways, since it is
now the year 2020.
Besides removing python2 as discussed on the linked page, there is currently
nicer way to force python3 that worked for me, by setting
{{-DPYTHON_EXECUTABLE=/usr/bin/python3}} CMake variable.
Related dispatch issue, DISPATCH-187
> Python detection logic prefers python2 over python3 when both are installed
> ---------------------------------------------------------------------------
>
> Key: PROTON-2217
> URL: https://issues.apache.org/jira/browse/PROTON-2217
> Project: Qpid Proton
> Issue Type: Bug
> Components: build, proton-c, python-binding
> Affects Versions: proton-c-0.31.0
> Reporter: Jiri Daněk
> Priority: Major
>
> I have the same experience that was reported elsewhere:
> bq. For me, the find_package(PythonInterp) call was always finding the older
> interpreter (2.7) even though everything pointed to the newer one (3.6).
> (from https://reviews.llvm.org/D64881)
> This behavior is unfortunate on Ubuntu 20.04 Focal, where both python2 and
> python3 are available, but pip for python2 is not packaged. Therefore it
> makes sense to build proton with python3; which would make sense anyways,
> since Python 2.7 is deprecated by the Python Software Foundation nowadays..
> Besides removing python2 as discussed on the linked page, there is currently
> nicer way to force python3 that worked for me, by setting
> {{-DPYTHON_EXECUTABLE=/usr/bin/python3}} CMake variable.
> Related dispatch issue, DISPATCH-187
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
