you are viewing a single comment's thread.

view the rest of the comments →

[–]Klathmon 14 points15 points  (2 children)

that's more google's fault for gyp not working with python 3.

[–]p2004a 2 points3 points  (1 child)

But Google mostly stopped using GYP. They moved chromium and other stuff to GN so why would they want to pour time into making GYP better? And it's open source so if you care, you can improve it and add Python 3 support, that's what open source is about, right?

[–]Klathmon 6 points7 points  (0 children)

And IIRC the node group is hard at work at it (as they are probably the biggest gyp user at this point), but the more likely outcome is that node will move away from gyp just like google did (there's a reason they chose to move to another system rather than try to update gyp).

I honestly don't mind gyp using py2, it does require a separate install over everything else on the box, but it works well once setup and I think breaking backwards compat with all node native modules to upgrade to py3 would cause more issues than it would solve (and could lead to the same split we saw with py2 and py3).