-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 24.0 #12441
Comments
Reminder to include this for 24.0 release. |
#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?
Alternatively, this seems like it would be a vendoring-updates-only release cycle which... I don't mind. :) |
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:
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. |
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. |
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. |
Works for me. |
I'll release 24.0 soon(ish). Please keep
|
Thank you for the new release!
Would be great to have this merged in time for Monday's 3.11 and Tuesday's 3.12 releases :) |
@sbidoul if you ping me when the CPython PR is ready, I can approve and merge it. |
@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. |
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... |
So things have been quiet, which is great. I'm therefore closing this release cycle. |
It's almost a new year!
The text was updated successfully, but these errors were encountered: