support Python 3 in v8 and inspector_protocol
Reported by
bmsd...@gmail.com,
Dec 4
|
||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36 Steps to reproduce the problem: Call any python script using python3 For example: `python3 tools/run-tests.py inspector --outdir out/x64.release/` What is the expected behavior? The script will execute What went wrong? We'll get an exception Did this work before? No Chrome version: 70.0.3538.77 Channel: dev OS Version: Flash Version: This task relates to these tasks: https://github.com/nodejs/node/issues/24512 https://bugs.chromium.org/p/chromium/issues/detail?id=898348
,
Dec 4
I don't think it's feasible to rewrite everything to python3.
,
Dec 5
I think that nothing is impossible) as cclauss@bluewin.ch says: https://github.com/nodejs/node/issues/24512 ``` There are now less than 400 days until the end of life of Python 2 (aka legacy Python). The v8 repo is just 1.4% Python but that is all legacy Python and at least 76 files need to be modified just to fix the print statement which is merely the start of a Python 3 port. v8 is a venerable codebase and I often hear that it has been a godsend to the JavaScript community but its Python code needs to be modernized, removed, or replaced with JavaScript, Go, etc. in the days remain (https://pythonclock.org/) until Python 2 end of life. ``` It will have to come to do sooner or later. I would like to try to do it gradually. The first touch I made here. https://chromium-review.googlesource.com/c/deps/inspector_protocol/+/1358520 And I plan to prepare for the update v8 |
||
►
Sign in to add a comment |
||
Comment 1 by swarnasree.mukkala@chromium.org
, Dec 4