Release 24.0

[pradyunsg]

It's almost a new year!

[FlavioAmurrioCS]

Reminder to include this for 24.0 release.
#12359

[pradyunsg]

#12300 (comment) -- @pypa/pip-committers Is there anything that we want to cut a 24.0 for in January, or should we skip this release month per our release cadence?

If there are no changes, then that release month is skipped and the next release will be 3 months later.

Alternatively, this seems like it would be a vendoring-updates-only release cycle which... I don't mind. :)

[notatallshaw]

While probably not being fixed by 24.0, I would like to make some noise about #12317, due to resolvelib/Pip stating requirements are impossible to resolve when they are not.

I have 2 PRs that could fix it:

• Revert backjumping sarugaku/resolvelib#142
• Add intelligent fallback from backjump to backtrack sarugaku/resolvelib#144

There are performance/complexity tradeoffs to decide.

And I do have a proposal and an intial PR that improves performance in those complex requirements situations: sarugaku/resolvelib#64 (comment). And so far in my testing makes the backjumping optimization relatively minimal. I plan to do more performance testing early in the new year.

[pfmoore]

I assume from the general lack of activity here (and the fact that it's the 25th January) that we're going to skip having a release in January. Let's pick this up in March, for the April release date.

[sbidoul]

There is the setuptools 69.0.3 compatibility issue that is resolved on main that might be worth doing a release.

If @pypa/pip-committers are fine with the content of https://github.com/pypa/pip/milestone/73, I can try and do a 24.0 release that includes that tomorrow.

[pfmoore]

Works for me.

[sbidoul]

I'll release 24.0 soon(ish). Please keep main quiet for a little while.

• prepare Release/24.0 #12505
• publish to PyPI
• push tag
• update get-pip Update to 24.0 get-pip#205
• release announcement https://discuss.python.org/t/announcement-pip-24-0-release/44912
• CPython PR gh-114965: Updated bundled pip to 24.0 python/cpython#114966

[hugovk]

Thank you for the new release!

[ ] CPython PR

Would be great to have this merged in time for Monday's 3.11 and Tuesday's 3.12 releases :)

[pfmoore]

@sbidoul if you ping me when the CPython PR is ready, I can approve and merge it.

[sbidoul]

@pfmoore I pinged you on the backport PRs, but I guess it's the RM's call whether such a fresh pip release is fit for for a cpython bugfix release.

[pfmoore]

I merged them on the basis that we've always put the latest pip releases into CPython before now. And there weren't any large changes in here. Fingers crossed...

[sbidoul]

So things have been quiet, which is great. I'm therefore closing this release cycle.