build: rm py semicolons (Python != JavaScript)

[MattIPv4]

Follow-up PR from #29105 (review) that applies Flake8 E703 (no semicolons) to all Python files.

Checklist

• commit message follows commit guidelines

[addaleax]

Can you undo the changes to deps/v8/ and tools/gyp/? Those are vendored in and not managed by this repository.

[MattIPv4]

Ah, do gyp changes need to occur in node-gyp?
Where do v8 changes need to be made?

[Trott]

Ah, do gyp changes need to occur in node-gyp?

I'm not sure to be honest. /ping @nodejs/node-gyp

Where do v8 changes need to be made?

Contributing to V8 is described at https://v8.dev/docs/contribute

[sam-github]

There is a chance that if @cclauss pushes a v8 change here, @targos can push it upstream into v8.

[cclauss]

For obvious reasons, I like this PR but... based @addaleax comment above this might not be the right forum.

1. The vast majority of the effected files are v8 which does not accept PRs at https://github.com/v8/v8 so landing takes effort that @Trott links to and @targos knows well.
2. The gyp files could be covered by a PR to https://github.com/nodejs/node-gyp.
3. build: py3 configure.py #29106 Already contains these changes for configure.py.
4. That leaves just one semicolon in tools/icu/shrink-icu-src.py that this PR could directly effect.

[MattIPv4]

@targos May you assist with getting these changes made to v8?

[Trott]

There was a conflict in deps/v8/tools/gen-postmortem-metadata.py, so I rebased and force-pushed.

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/25028/

[Trott]

4. That leaves just one semicolon in tools/icu/shrink-icu-src.py that this PR could directly effect.

Reworked the commit here (preserving authorship) and opened #29170.

Going to close this, since it shouldn't land, but feel free to continue discussion about getting the changes upstreamed to V8. If you think it should be open for any reason, go ahead and re-open (or if GitHub won't allow that, post a comment asking that it be re-opened).

[MattIPv4]

Sounds good. Hopefully, someone can help land the v8 changes 👍

[rvagg]

sorry, just for clarity I'll address:

Ah, do gyp changes need to occur in node-gyp?

I'm not sure to be honest. /ping @nodejs/node-gyp

They are not in sync, a PR here should be followed by a PR to node-gyp, ideally, and vice versa. We're still trying to figure out how to maintain this mess.

[MattIPv4]

@rvagg As I've got the PR open in node-gyp already, should I create a separate one in node that duplicates those changes?

[rvagg]

@MattIPv4 yep, I think so, if they're changes for tools/gyp then it's probably worth doing, we're out of sync already and don't have a process to get back into sync yet so doing things manually isn't going to hurt for now.