build: find Python 3 or Python 2 in configure by cclauss · Pull Request #25878 · nodejs/node (original) (raw)

I don't think this is blocked by #25878, its blocked by using a python version that won't actually work for configure, isn't it?

The steps to python3 are
1a - node can be built, tested, etc using python2 if available, and python3 if it isn't or if python3 is deliberately requested. This can likely be done in a single PR, maybe #28537 is better for that? This step is backwards compatible, and allow local development and testing with python3.
1b - python3 needs to exist on all build infrastructure

--- these can be done in parallel, they don't block each other

2 - convert configure to use python3 when available, falling back on python2 if not. This is probably backwards compatible, and will cause the python3 installed in 1b to start to get used, so we can see how well it works across all our platforms.

3 - remove python2 support (after a while, possibly in the next major release post-python2.7 EOL)