-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
Support python3 #2893
Comments
I'm happy to do this, I think it'll be straightforward, but it's probably worth waiting for v8 support to be completed. |
@cclauss I bet I can do the deno part of the port in under an hour, certainly less than a day. I've ported large modules to python 3... deno is very small. I suppose it would help to enumerate precisely which python v8 scripts need to be ported in order for deno to work, I can do that. |
Not a question of your skills. I have been impressed. It is just a question of putting lots of concentrated pressure on the few bottlenecks that are not ready so we create a compelling reason to act. We want to create the impression that the train is leaving the station without the laggards onboard. |
Hi! |
https://travis-ci.com/bmsdave/v8/builds/132539826 |
@bmsdave Can V8 be built with Python 3? |
https://travis-ci.com/bmsdave/v8/builds Seems to be passing the lint steps. Where does the V8 build on Py3 break down? |
The script it's running is |
Exactly. So where can we see the build failing on Python 3? |
Sorry I was answering (no) to @kt3k :
It could be that the build works with just the syntax changes (but I would be surprised). I think we need to compile and run with gm.py, see https://v8.dev/docs/test. |
We are heavily dependent on V8, which in turn is heavily dependent on Chromium tooling, which does not support Python3 and has only recently begun conversion -
https://bugs.chromium.org/p/chromium/issues/detail?id=942720
https://bugs.chromium.org/p/v8/issues/detail?id=8594
nodejs/node#24512
The text was updated successfully, but these errors were encountered: