-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Building for GLIBC 2.27? #10
Comments
I believe Nodejs 18 dropped Ubuntu 18 and Centos/RHEL 7/8 support, and I think Google Colab may be running on a Debian/Ubuntu derived Linux of that vintage. Installing with:
or
works. (Note that the 'a4' for alpha is not a Node alpha, it's the alpha version of this pypi package. I think we are confident that we have a working package and will start doing proper releases soon.) |
Thanks @samwillis for the info! Unfortunately we're using some of the latest and greatest node features in nodejs 18. Sounds like we may just have to skip support for Google Colab until Google updates their OS. |
If the package requires glibc 2.28, why not release manylinux_2_28 wheels? Please see PEP-600.
|
Thanks for the info, I had missed that. Will update! |
@samwillis I would feel comfortable taking this on once we have the CI setup in place so that we can use docker to emulate the OS environment reported by @njzjz |
@jacobdr Go ahead, that would be great. |
@njzjz one thing I am slightly confused about... We do publish a Can you send the output please from running |
@jacobdr I think you misunderstand what I mean. If you use GLIBC 2.17, the This does not affect any one who has GLIBC 2.28. |
This is a great project, and we are looking forward to using it!
In some initial testing on various Python platforms, we see that Google Colab is using Python 3.7 using GLIBC 2.27. That gives an error when using nodejs-pypi:
What would it take to build nodejs-pypi to work on Google Colab GLIBC 2.27?
The text was updated successfully, but these errors were encountered: