Release 25.0

[ichard26]

I'm filing this early, but given the current pace of development, it can't possibly hurt :)

Looking at the current state of the milestone, there are a handful of deprecated features scheduled for removal during this release cycle:

• Removal of egg support entirely (Remove support for installed eggs distributions #12308) [actually scheduled for pip 24.1]
• Removal of --build-option and --global-option (Remove --global-option and --build-option flags #12301) [deferred]
• Removal of the legacy editable install mechanism

There's also the upgrade to vendoring 1.1.0 which will bring significant improvements.

@sbidoul, is setuptools any closer to being prepared for the removal of --build-option and --global-option?

[ichard26]

Oh! and how I could forgot the last major potential change: removal of Python 3.8 support. I haven't looked at the numbers recently, but we need to consider that as well.

[sbidoul]

is setuptools any closer to being prepared for the removal of --build-option and --global-option?

I don't think so. I filed #13106 accordingly.

[ichard26]

For whoever decides to be the next RM, just a heads-up: we'd like to switch to using an action to build (not prepare) and push the release, using Trusted Publishing and all of the new fancy stuff that comes with that. See #13048.

[ichard26]

Looking closer at my schedule, I will be too busy to be a RM right until January 30 next year, so if there is no one that is able to be the RM, I could do it on either a tight schedule (aka that weekend) or push the release by a week or two. Of course, I'm also new at this, so I'd definitely want to have a former RM available for questions :)

[sbidoul]

I'm happy to take on the RM hat for this release again. I'll take the opportunity to test and document the trusted publisher workflow.

[ichard26]

I'm planning to spend time starting this Friday on the legacy editable install removal.

• The actual PR removing support for legacy editables - I'm rather unfamiliar with this part of the codebase, so I'm probably going to need help, but I'd like to at least try to take a stab at this
  • Ensuring that the error messaging is crystal clear and provides user-friendly actionable advice
• A bunch more communication work
  • Rewriting all of the things I've said about this deprecation into a single blog post that is focused on this deprecation for better SEO (over my pip 24.2/24.3 posts)
  • Write a StackOverflow Q&A for the eventual error
  • Write a documentation page for this...? (I may use this as an excuse to finally set up the error index we've been meaning to set up)

I'm still relatively unfamiliar with the codebase, so I've decided that I can best contribute by working through the admin and communication work needed to support this release. Historically, this project hasn't done the best w/ communication (barring the time we had a paid PM) and I'd like to improve that if I can :)

[ichard26]

I do want to take another look at the open PRs and see if there's anything else I'd love to see in the next release, but for now, maintainer eyes would be appreciated on the following issues/PRs targeting 25.0

• Vendor resolvelib 1.1.0 #13001
• Add trusted publisher release workfiow #13048 (I do realize that I need to reply myself)
• Never use the pkg_resources metadata backend on python 3.13+ #13010
• Drop support for Python 3.8 #12989