build: Python pip no longer has a --no-user option

[cclauss]

As discussed in nodejs/build#3273

A --no-user option was added to pip 5 years ago but was later removed.

• https://github.com/pypa/pip/pull/5116/files

[mhdawson]

LGTM

[cclauss]

Are we OK with the four failing tests?

• node-test-commit
• node-test-commit-plinux-rhel8-ppc64le
• node-test-linux-linked-shared
• node-test-linux-linked-withoutintl

[Qard]

I'm guessing those are probably flakes. They don't look related.

[nodejs-github-bot]

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

[nodejs-github-bot]

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

[nodejs-github-bot]

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

[nodejs-github-bot]

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

[github-actions]

A commit referencing this Pull Request was pushed to by @cclauss without the expected commit metadata added to its message.

[aduh95]

This landed without the correct metadata, without the required wait time (at the time of writing, this PR needs to wait 5 more hours to land), and without a passing CI (although I'm unsure Jenkins CI is a requirement for this change). I've force-pushed to remove the commit, please open a new PR and use the commit-queueAdd this label to land a pull request using GitHub Actions. label instead of the "Squash and merge" button.

[Trott]

I re-opened this as #47372 (maintaining commit authorship--I think the commit-queue bot sometimes does funny things with it, though, so I might recommend landing manually). I will start CI there and request fast-tracking.

[cclauss]

I sense that the commit message linter did not like that I capitalized the word Python.

In the Python community, we say that python is a snake and Python is a programming language.

[tniessen]

I sense that the commit message linter did not like that I capitalized the word Python.

@cclauss The commit message check that was triggered when you pushed d8e3fca4a521d4ed6def274df75869284785b713 did not fail because of the commit message title. It failed (and sent a warning to the #nodejs-core Slack channel) because you pushed a commit to the main branch that was missing mandatory metadata.

✖ d8e3fca4a521d4ed6def274df75869284785b713
✔ 0:0 no Co-authored-by metadata co-authored-by-is-trailer
✔ 0:0 skipping fixes-url fixes-url
✔ 0:0 blank line after title line-after-title
✔ 0:0 line-lengths are valid line-length
✔ 0:0 metadata is at end of message metadata-end
✖ 0:0 Commit must have a PR-URL. pr-url
✖ 0:0 Commit must have at least 1 reviewer. reviewers
✔ 0:0 valid subsystems subsystem
✔ 0:0 Title is formatted correctly. title-format
✔ 0:0 Title is <= 50 columns. title-length

This PR was also merged in violation of other rules as @aduh95 described above. You can find the collaborator guide here.