July 2022 release (22.2)

[pradyunsg]

It's another quarter, another release.

[pradyunsg]

Who wants to be release manager for this one? :)

It's due by the end of this month and we have 6 PRs that are open and still in this milestone. We have one deprecation-related removal, which I'll file a PR for today.

[sbidoul]

As I will not be available to do 22.3 in October, I'm happy to take this one.

I plan to do it between the 21st and 24th, assuming some other maintainers would be around to help handle any fallout of the riskiest features.

[sbidoul]

I tried the vendoring upgrade and our patch to requests does not apply cleanly.

IIUC #10174, this patch is to make requests use chardet instead of charset_normalizer, and it was done because html5lib requires chardet ?

Now that our use of html5lib has been behind a deprecated feature flag for 2 releases, maybe we should drop html5lib now, and vendor charset_normalizer instead ?

[pradyunsg]

Looks like that was the plan in #10825, so let’s do that!

[sbidoul]

Now that our use of html5lib has been behind a deprecated feature flag for 2 releases, maybe we should drop html5lib now, and vendor charset_normalizer instead ?

Update: in the end I dropped html5lib, but I did not vendor charset_normalizer because we vendor pygments which also tries to import chardet. Granted, pygments is a dependency of rich and we don't use it, but I did not feel like doing additional patching of vendored dependencies right now.

[sbidoul]

Alright, almost there. I plan to release on Thursday.

If there is anything else that is ready to go in, let me know.

@pradyunsg do you plan to release a new version of packaging by then ?

[sbidoul]

I'm drafting the announcement at https://hackmd.io/Wie2Ge87SZKKoaimYA4ppw. @pypa/pip-committers your input is welcome.

[pfmoore]

LGTM 🙂

[sbidoul]

Uploading to PyPI now.

[sbidoul]

get-pip updated and annoucement posted.

Everything went smoothly. Kudos for the release process, @pradyunsg !

I'll do the cpython part over the weekend, if nothing horrible has happened with the release by then.

[pfmoore]

Ping me if you need a core dev to merge the ensurepip change.

[pradyunsg]

I think CPython is non-trivial, since we need to update ensurepip's code. I've been procrastinating on that, but maybe the pip runner changes have eliminated the need for that?

[sbidoul]

@pradyunsg you mean python/cpython#92688 (comment) ? Is it not resolved by #11183 ?

[pradyunsg]

Yup, and I misremembered the cause of the issue! (just like I mistapped the wrong button now)

[pradyunsg]

There's some discussion about a breakage due to an interaction of pip 22.2's new importlib-based injection and setuptools' distutils injection in #11294. I'll file a PR if the discussion results in a conclusion that we need to change something on our end.

[sbidoul]

Note to self: python 3.11.b5 is expected on Monday 2022-07-25, and rc1 the week after.

[sbidoul]

Alright, nothing dramatic happened with 22.2, but still there will be a 22.2.1. So I'm not sure if I should push 22.2 to CPython now, or wait a little bit until #11238 (comment) and #11288 land.

[pradyunsg]

My 2c: Let's get 22.2 included, since we missed the last pip upgrade being included in ensurepip. That way, even if 22.2.1 doesn't go in by the time the next Python beta comes out, at least we'll have a version of pip that uses sysconfig out-of-the-box be a part of CPython.

[sbidoul]

My 2c: Let's get 22.2 included, since we missed the last pip upgrade being included in ensurepip. That way, even if 22.2.1 doesn't go in by the time the next Python beta comes out, at least we'll have a version of pip that uses sysconfig out-of-the-box be a part of CPython.

Makes sense. I'll do that right now.

Question: shall I upgrade the bundled setuptools at the same time? Or is it something the setuptools maintainers should do?

[pradyunsg]

I don't think we've updated setuptools the last couple of times (we hit issues IIRC), and I'd defer to the setuptools maintainers for that.

The last time -- I upgraded setuptools and I filed a separate PR for it. That's probably the way to go here, in case it ends up staying open due to some compatibility issue from the setuptools upgrade. The last setuptools upgrade was reverted for a similar reason, and that's what I'd remembered when I wrote the initial comment here.

[sbidoul]

Alright, so I filed python/cpython#95195 for pip, and I'll do setuptools when that one is merged (since they would likely conflict with each other).

[pradyunsg]

They won't -- they either modify different files or completely disjoint set of lines in the same file. :)

[pfmoore]

ensurepip updates for pip and setuptools have now been merged into main, 3.11 and 3.10 branches.

[pradyunsg]

Hurrah! Thanks for doing that @pfmoore and @sbidoul! ^>^

[sbidoul]

@pypa/pip-committers for the time being, could you merge to main only things that need to go in 22.2.1 ? That will save me some chrerry-picking work.

[sbidoul]

I just released 22.2.1.

@pfmoore the CPython PR is python/cpython#95340

[pfmoore]

... and it's merged into CPython

[pradyunsg]

@sbidoul Do you want us to hold off on merging PRs further, or is main open for regular development? :)

[sbidoul]

Things I know of that may require a 22.2.2 are #11319, #11314 and #11288. But I don't know if nor when that will happen or warrant a patch release.

So yes, I think we can open main for regular development.

[sbidoul]

We got 3 issues fixed in the 22.2.2 milestone. If nothing else shows up, I'll cut the release later this week, and this will hopefully close the 22.2 cycle.

[sbidoul]

And 22.2.2 is out.

@pfmoore here is the cpython PR: python/cpython#95610

[pfmoore]

Merged into main, 3.11 and 3.10

[pradyunsg]

@sbidoul Is there anything else needed here, or can we close out this release cycle? :)

[pradyunsg]

I believe he's AFK for the near future, and we can reopen this if there's need for another bugfix.

[sbidoul]

I'm a aware of #11352 (which is a minor regression on python 3.11) and I'm keeping an eye on #11349 (which is unexplained so far). At this stage I'm good with closing the 22.2 cycle unless there is something important to include in the Python 3.11 release.