tools: update gyp-next to v0.9.1

[gengjiawen]

No description provided.

[nodejs-github-bot]

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

[ryzokuken]

By the way, since there's no patches floating on top of gyp-next anymore, should we just make it a git submodule?

(also, there is a newer patch version out, maybe you'd like to switch to that version?)

[nodejs-github-bot]

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

[nodejs-github-bot]

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

[nodejs-github-bot]

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

[nodejs-github-bot]

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

[nodejs-github-bot]

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

[nodejs-github-bot]

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

[gengjiawen]

Landed in ffdaf47

[targos]

We forgot to run V8 CI and it is now broken: https://ci.nodejs.org/job/node-test-commit-v8-linux/4031/nodes=benchmark-ubuntu1604-intel-64,v8test=v8test/console

@richardlau Do you think it's possible to make it a hybrid build (use Python 2 for V8 and Python 3 for Node.js) ?

[richardlau]

We forgot to run V8 CI and it is now broken: https://ci.nodejs.org/job/node-test-commit-v8-linux/4031/nodes=benchmark-ubuntu1604-intel-64,v8test=v8test/console

@richardlau Do you think it's possible to make it a hybrid build (use Python 2 for V8 and Python 3 for Node.js) ?

Yes. #38969 is one possibility. Another would be to not create the python override symlink at all and update all gyp actions that call python to call python3¹ but I'd consider that a riskier change.

¹FWIW the gyp documentation for actions recommends

For maximum cross-platform compatibility, invocations that require a Python interpreter should be specified with a first element "python". This will enable generators for environments with specialized Python installations to be able to perform the action in an appropriate Python environment.