Update to packaging 20.9

[henryiii]

Ran with vendoring sync . -v.

Preparation for #9506; fixes an issue with pip not installing 10.9+ Universal2 wheels on ARM macOS.

[pfmoore]

Thanks. What's with the "chore:" in the commit message and PR title? As an entirely trivial style point (i.e. if you don't I won't worry) I'd prefer if it were omitted.

[henryiii]

Habit, from https://www.conventionalcommits.org/en/v1.0.0/ - chore being for updates.

[henryiii]

Should I bump everything from pipenv run nox -s vendoring -- --upgrade ? It ran fine on macOS, there are 4 bumps:

Upgrade urllib3 to 1.26.3
Upgrade idna to 3.1
Upgrade certifi to 2020.12.5
Upgrade packaging to 20.9

[henryiii]

Nice, it even adds the news entries. :)

[henryiii]

Next time I'm using pipx, seems like nox -s vendoring wants to add my Pipfile/Pipfile.lock.

[henryiii]

I've cherry picked one commit from the four (and removed the Pipfiles it added to the commit 😠 ). Rerunning with pipx run nox -s vendoring -- --upgrade was much better, didn't add extra files - I can switch to the four commits if you'd rather everything bumped. Or I can do separate PRs, if you prefer everything bumped but one-per-PR.

[pfmoore]

Sorry, I don't have time to look at this, maybe one of the other @pypa/pip-committers does.

[uranusjr]

I trust vendoring is doing the right thing and did not check the updated code in packaging, only the file names affected.

[pradyunsg]

LGTM!

Next time I'm using pipx, seems like nox -s vendoring wants to add my Pipfile/Pipfile.lock.

The automation is written with the assumption that you have a clean working tree. 🤷🏻‍♂️