Addon-WG: Bundle CPython into Addon Tooling

TL;DR

Bundling Python on unix is really simple . Exchanging data (e.g. objects) as well. Feels a bit like compiling the whole Python-lang though and runs for 2+ mins. Was attempting this at eljefedelrodeodeljefe/node-cpython in order to run py-libs natively.

Disclaimer
It's a working API but not tested currently (left that for vacation next week)

I am doing lot's of native addon building and figured out that compilation can be a real pain. I was investigating on this for quite a while and wanted to propose shipping Python.h and exposing a high level API (streams as well) to JS in order to be able to abstract gyp.
It would render you to not just call .exec() on it, but having it in cpp-land.

@bnoordhuis would that be something worth a discussion? (pointing at you since you were talking about this in the last CTC and I liked your opinions in Berlins Code and Learn)

I think it has been mentioned a lot that gyp will not change and especially the python-2.7 dependence is quite annoying. With the above approach, one could just choose which version to run from JS.
Also it would enable one to slowly deprecate some of the gyp or python tooling, by keeping the API, but exchanging the below implementations with JS stuff.

Maybe this would ease the multitude of node-gyp problems on Windows, as an example.

Start by reviewing the proposal and its linked node-cpython project, then consider how Python.h, CPython bundling, streams, and a high-level JavaScript API would relate to node-gyp and gyp. No repository files or tests are named; the work is not ready until the scope and implementation approach are agreed.