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

doc: remove outdated footnote (Python 2 --> 3 for V8 tests) #43105

Conversation

DeeDeeG
Copy link
Contributor

@DeeDeeG DeeDeeG commented May 14, 2022

Various Python 3 compatibility fixes were made in upstream V8,
and they have even dropped Python 2 compatibility in various scripts.

depot_tools, which bootstraps the V8 build, is also moving to Python 3.

As of Node v18.0.0-ish, this footnote is no-longer accurate.

(Running make test-v8 no-longer requires Python 2,
and it won't work anymore if you don't have a copy of Python 3.)

Various Python 3 compatibility fixes were made in upstream V8,
and they have even dropped Python 2 compatibility in various scripts.

depot_tools, which bootstraps the V8 build, is also moving to Python 3.

As of Node v18.0.0-ish, this footnote is no-longer accurate.

(Running `make test-v8` no-longer requires Python 2,
and it won't work anymore if you don't have a copy of Python 3.)
@nodejs-github-bot
Copy link
Collaborator

Review requested:

  • @nodejs/tsc

@nodejs-github-bot nodejs-github-bot added the doc Issues and PRs related to the documentations. label May 14, 2022
@DeeDeeG
Copy link
Contributor Author

DeeDeeG commented May 14, 2022

Oops, the XCode stuff is presumably still accurate on macOS. Maybe that should be kept...

Edit: I pushed a commit to address this. (Should probably be squashed, but I know force pushing to open PRs is frowned upon...)

Restore unintentionally deleted bit of the footnote.

(I haven't checked whether just the "command line tools" are enough now.
So it's safer to assume this part of the footnote is still accurate,
than to assume the requirements have changed.)
@Trott
Copy link
Member

Trott commented May 15, 2022

@nodejs/v8-update

@Trott Trott added the commit-queue-squash Add this label to instruct the Commit Queue to squash all the PR commits into the first one. label May 15, 2022
@Trott Trott added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label May 15, 2022
@aduh95 aduh95 added the commit-queue Add this label to land a pull request using GitHub Actions. label May 22, 2022
@nodejs-github-bot nodejs-github-bot removed the commit-queue Add this label to land a pull request using GitHub Actions. label May 22, 2022
@nodejs-github-bot nodejs-github-bot merged commit 5d9ad80 into nodejs:master May 22, 2022
@nodejs-github-bot
Copy link
Collaborator

Landed in 5d9ad80

bengl pushed a commit that referenced this pull request May 30, 2022
Various Python 3 compatibility fixes were made in upstream V8,
and they have even dropped Python 2 compatibility in various scripts.

depot_tools, which bootstraps the V8 build, is also moving to Python 3.

As of Node v18.0.0-ish, this footnote is no-longer accurate.

(Running `make test-v8` no-longer requires Python 2,
and it won't work anymore if you don't have a copy of Python 3.)

PR-URL: #43105
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
Reviewed-By: Darshan Sen <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Jiawen Geng <[email protected]>
Reviewed-By: Akhil Marsonya <[email protected]>
Reviewed-By: Jackson Tian <[email protected]>
@bengl bengl mentioned this pull request May 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
author ready PRs that have at least one approval, no pending requests for changes, and a CI started. commit-queue-squash Add this label to instruct the Commit Queue to squash all the PR commits into the first one. doc Issues and PRs related to the documentations.
Projects
None yet
Development

Successfully merging this pull request may close these issues.