Added blocked label as per original description.

Ping @cclauss

@BridgeAR What do you want me to do?

I should have read the reasons why there was a -1. Sorry for the ping.

Some experimentation here says that we will face an issue with Python 3.7 because async is a reserved word in Python >= 3.7 #29326 so using that word in the wrong context is a Python syntax error. So for initial experimentation, I plan to start with Python 3.6.7.

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)

CI: https://ci.nodejs.org/job/node-test-pull-request/25293/

Removing the blocked label based on #25878 (comment) and the lack of a response to #25878 (comment)

./configure --ninja still won't work on python3. Trying to make a patch soon.

#29414 allow legacy Python to continue to use cStringIO.StringIO

@thefourtheye I think your requested change was done, can you please re-review?

@thefourtheye Sorry, I found your requested change:

Apart from the reasons mentioned in the original description, all the dependencies should be Python 3 compatible for this to work.

I don't agree that this is a pre-req for this to land on master. Its blocked from 12.x, but on master it does no harm, it just changes a "no supported python 2.7 found" error to (possibly) an python3 incompatibility error. It causes no harm (or change) to a system that already would have built.

@thefourtheye , please re-review

Is something blocking us from landing this one?

@thefourtheye has a blocking review, but doesn't seem to be resonding to request to relook. @nodejs/tsc, is 5 days with no response enough to dismiss a review, or should we wait more? What is the convention here?

@thefourtheye has a blocking review, but doesn't seem to be resonding to request to relook. @nodejs/tsc, is 5 days with no response enough to dismiss a review, or should we wait more? What is the convention here?

@sam-github There's no set rule, but 5 days of non-responsiveness strikes me as a reasonable amount of time to wait before dismissing the request-for-changes.

@thefourtheye has a blocking review, but doesn't seem to be resonding to request to relook. @nodejs/tsc, is 5 days with no response enough to dismiss a review, or should we wait more? What is the convention here?

@sam-github There's no set rule, but 5 days of non-responsiveness strikes me as a reasonable amount of time to wait before dismissing the request-for-changes.

Not necessary, but it may be a reasonable courtesy to also email the Collaborator who hasn't responded and then wait, say, 48 hours. Sometimes people just don't see stuff because of overwhelming GitHub notifications.

@thefourtheye has a blocking review, but doesn't seem to be resonding to request to relook. @nodejs/tsc, is 5 days with no response enough to dismiss a review, or should we wait more? What is the convention here?

@sam-github There's no set rule, but 5 days of non-responsiveness strikes me as a reasonable amount of time to wait before dismissing the request-for-changes.

Not necessary, but it may be a reasonable courtesy to also email the Collaborator who hasn't responded and then wait, say, 48 hours. Sometimes people just don't see stuff because of overwhelming GitHub notifications.

I just emailed @thefourtheye now.

Sorry, this was blocked because of me. I just re-reviewd now and LGTM.

CI: https://ci.nodejs.org/job/node-test-pull-request/25416/

CI: https://ci.nodejs.org/job/node-test-pull-request/25418/

Landed in be926c7