Cut a 24.0.1 release that is compatible with Python 3.13 before vendoring new version of packaging

[notatallshaw]

What's the problem this feature will solve?

When #12300 lands there will be packages that from that point on will likely be permanently incompatible with pip, e.g. textract, because they use legacy versions or specifiers.

Yet, this may be the only reason they are incompatible with Python 3.13+. However pip 24.0 is incompatible with Python 3.13 but main is not due to #12462 being merged after 24.0 was released.

This will allow the workaround for users, who do not have the ability to fork the relevant projects, on Python 3.13 to install pip==24.0.1

Describe the solution you'd like

• Add Python 3.13 to the CI tests
• Fix any issues
• Release a 24.0.1 version of pip

Alternative Solutions

Advise users to either:

• Fork the broken project
• Use uv to install packages with legacy versions of specifiers

Additional context

This is to create a short/medium term workaround for users who get stuck because they are not technically proficient enough to fork and they are, for some reason, required to use Python 3.13.

This is not meant as a long term workaround, and could break for Python 3.14.

Code of Conduct

• I agree to follow the PSF Code of Conduct.

[notatallshaw]

btw, I'm happy to add the CI tests and fix any issues, I can take a look once I get home tonight.

[notatallshaw]

First blocker I found for running tests, freezegun will need to do a release spulec/freezegun#534

[notatallshaw]

I created #12620, it looks like while pip seems to run fine on Python 3.13, getting the whole CI test suite running will be at least a few weeks away.

[notatallshaw]

Closing as #12300 (comment) suggests that #12462 is no longer a requirement to work on Python 3.13.

I will continue to work on updating Python 3.13 CI PR, but with this news it seems like a 24.0.1 is no longer required.