Bug 1485 - libsigrok should look for python 3 and use it, if 'python' is python 2.
Summary: libsigrok should look for python 3 and use it, if 'python' is python 2.
Status: CONFIRMED
Alias: None
Product: libsigrok
Classification: Unclassified
Component: Build system (show other bugs)
Version: unreleased development snapshot
Hardware: All All
: Normal normal
Target Milestone: ---
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-01-05 18:42 CET by Martin Ling
Modified: 2020-01-05 18:42 CET (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Ling 2020-01-05 18:42:15 CET
It's 2020. Python 2 is finally dead. Long live Python!

https://www.python.org/doc/sunset-python-2/

However, when I build libsigrok on Debian, it still automatically detects the python 2.7 interpreter installed as 'python' and builds/installs bindings for that, rather than finding 'python3'. This situation will probably persist on many distributions for a long time.

There's a strong argument that now that Python 2 is finally sunsetted, we should simply refuse to build against it any more. In that case, we need to automatically detect this situation and look for python3.

But even if we don't outright refuse to build against python 2, we should definitely no longer do it by default. Which means that we still need to detect this situation and look for python3.

So either way, we need the build system to go looking for python 3.