Skip to content
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

Closed
abersheeran opened this issue Mar 6, 2019 · 16 comments
Closed

Why no support Python3 #1687

abersheeran opened this issue Mar 6, 2019 · 16 comments

Comments

@abersheeran
Copy link

abersheeran commented Mar 6, 2019

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?

@Ryanhui
Copy link

Ryanhui commented Mar 11, 2019

use python3, please.

@LincePotiguara
Copy link

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.
There are some build systems trying to mitigate this like cmake-js.

@nodejs nodejs deleted a comment from abersheeran Mar 11, 2019
@raf202
Copy link

raf202 commented Mar 24, 2019

+1 for Python3

@einarpersson
Copy link

+1

@bnoordhuis
Copy link
Member

In the works, see other open issues and pull requests.

@ngocdaothanh
Copy link

Hello, is there any progress yet?

@cclauss
Copy link
Contributor

cclauss commented Sep 3, 2019

Yes.

@skewty
Copy link

skewty commented Sep 5, 2019

python: accept Python 3 conditionally (João Reis) #1815

Shouldn't this be re-opened until a release is made with unconditional python3 support?

Is requiring NODE_GYP_PYTHON3 not a breaking change?

@actuallymentor
Copy link

Yes.

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).

@cclauss
Copy link
Contributor

cclauss commented Sep 18, 2019

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.

@actuallymentor
Copy link

It would be great if you could create a markdown file explaining how to experiment with Python 3

What exactly do you mean? A migration guide for Py2 to Py3 or the logistics of managing python versions when developing?

@cclauss
Copy link
Contributor

cclauss commented Sep 20, 2019

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.

@actuallymentor
Copy link

actuallymentor commented Sep 27, 2019 via email

@cclauss
Copy link
Contributor

cclauss commented Sep 27, 2019

node-gyp v5.0.4 landed in #1893 so we no longer need the markdown file.

@Wegazz
Copy link

Wegazz commented Oct 13, 2019

+1 for Python3

@rvagg
Copy link
Member

rvagg commented Oct 13, 2019

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.
If you have a Python 3 bug to report please submit a new issue or pull request.

@nodejs nodejs locked as resolved and limited conversation to collaborators Oct 13, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests