-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Why no support Python3 #1687
Comments
use python3, please. |
So, this February 2013 issue #193 say that the node staff is aware of the problem and trying to work on it. And the gyp staff are also aware as this 2009 issue shows. |
+1 for Python3 |
+1 |
In the works, see other open issues and pull requests. |
Hello, is there any progress yet? |
Yes. |
Shouldn't this be re-opened until a release is made with unconditional python3 support? Is requiring |
Is there any (code) thing I/we can do to support? This has been an issue for a long time now (not referencing this issue #1687 but the build issue). |
It would be great if you could create a markdown file explaining how to experiment with Python 3. I believe that those instructions would give others more confidence to try it out an provide feedback and pull requests. |
What exactly do you mean? A migration guide for Py2 to Py3 or the logistics of managing python versions when developing? |
A Experimenting with Python 3.md file for... As a software developer, I want to build and run GYP on Python 3 so that I can be confident about what works and so that I can submit pull requests and open issues where I see bugs and blockers. |
Are you not just referring to a python 2 -> 3 migration guide? Which are in
the python docs here: https://docs.python.org/3/howto/pyporting.html
…On Fri, Sep 20, 2019, 10:40 Christian Clauss ***@***.***> wrote:
A *Experimenting with Python 3.md* file for...
As a *software developer* want to *build and run GYP on Python 3* so that
I can *be confident about what works and so that I can submit pull
requests and open issues where I see bugs*.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1687?email_source=notifications&email_token=ACFGWFSOYJ6IUBZGEUEQWI3QKSD5VA5CNFSM4G4BUPCKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7GAKVQ#issuecomment-533464406>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACFGWFUQWWXC4PMYKC6EUWLQKSD5VANCNFSM4G4BUPCA>
.
|
node-gyp v5.0.4 landed in #1893 so we no longer need the markdown file. |
+1 for Python3 |
Please don't comment or +1 this issue. We consider it closed. Python 3 is supported in the latest versions. 5.0.5 and 6.0.0 are out and have solid Python 3 support. If you don't have those versions then please upgrade. The latest npm has one of them so upgrade npm if you need to. |
Python2 has nine months left to live, so why not move to Python3?
If you don't use Python3, please don't use Python. Can't replace Python with JavaScript?
The text was updated successfully, but these errors were encountered: