In #298, @jacobwgillespie discovered that homebrew has started installing Python 3 by default, which breaks node-gyp. We should call this out explicitly in the macOS installation docs.
Arch linux-based distros do this as well, where which python is a symlink to python3
Maybe this is answered else where but what is the plan for 1/1/2020?
When python 2.7 is no longer maintained?
@kjvalencik let's move this conversation to http://github.com/neon-bindings/website/issues
I think we should keep this open to help track the progress on node-gyp. For what it's worth, node-gyp is an incredibly vital part of the node ecosystem.
@maxdobeck My understanding is that python 3 support for node-gyp is being worked on. At this point, I think it may be prudent to wait and see.
I propose to close this issue because the Getting Started Guide states "Python 3 is not supported" for all platforms.
However, I would also like to know if this is still the case, and if so, whether it will remain the case, and if there are any issues filed for that.
Edit: my understanding is that node-gyp itself supports recent versions of python, but being new here I don't know if this translates directly into python3 support for neon.
Seems like node-gyp now supports python 3
First, thank you for this project! it is a real boost to creating fast interop between JS and rust for developer tools.
As pointed, node-gyp does support Python 3 now. I am curious what the status is on this project regarding that? Would help simplify the usage of this library for me (and likely others)
Keep up the great work!
@ScottAwesome If node-gyp supports python3, so should neon. If for some reason it's not working, it could be that node-gyp version needs to be bumped, but I thought we did that.
In either case, we are finishing up the n-api backend which doesn't require node-gyp or python at all. It only requires node and cargo.
@ScottAwesome If node-gyp supports python3, so should neon. If for some reason it's not working, it could be that node-gyp version needs to be bumped, but I thought we did that.
In either case, we are finishing up the n-api backend which doesn't require node-gyp or python at all. It only requires node and cargo.
@kjvalencik if I opened a PR documenting this, would that be cool? or is there any other reason to hold off that I'm just not thinking of?
@ScottAwesome I think we can close this issue. I'm pretty sure that Neon has worked with Python 3 for awhile. I checked and confirmed that CI is running with Python 3.
Most helpful comment
@ScottAwesome If node-gyp supports python3, so should neon. If for some reason it's not working, it could be that node-gyp version needs to be bumped, but I thought we did that.
In either case, we are finishing up the n-api backend which doesn't require node-gyp or python at all. It only requires node and cargo.