Please make a new release

[intgr]

The last release of requests was from June 29.

Since then charset-normalizer 3.x has been released, which the release is incompatible with. This was already fixed in #6261, but is unreleased.

Clearly this affects many people, as this issue has been re-reported so many times:

• charset-normalizer 3 is out, but unfortunately is incompatible with the current version of the requests. #6268
• RFE: support for charset_normalizer >= 3 #6272
• Conflicting version with charset-normalizer #6298
• charset-normalizer upgraded to 3.x #6288
• Broken dependency with latest charset-normalizer #6305
• requests 2.28.1 is imcompatible with charset-normalizer 3.0.0  #6281
• Support charset-normalizer>=3 #6273
• RFE: support for charset_normalizer >= 3 #6272

If even just to stop people from wasting their time re-reporting this, please make a release.

[nateprewitt]

Thanks for the feedback, @intgr. As already stated in the other issues, this has been merged and will be in the next release 2.29.0.

[intgr]

Why are requests project maintainers so dismissive... I am fully aware that the PR was merged and will be in the next release, I already stated as much in my message.

But there is no planning/tracking issue or discussion about a release that I could find.

What are the plans for the next release? Is it going to happen within days or months? Or is it still waiting for some blockers?

[sigmavirus24]

Why do you feel entitled to demanding we do something in our free time?

Why do you think we don't know we need to release it? Issues like this just take what little time we might otherwise have had to work on the release and wastes it.

You argue that we're wasting other people's time when the issues have been indexed by Google and are easily searchable on GitHub. So they're eating their time as well as ours. We're not responsible for people choosing to create duplicate issues when the original is easily found. We're not responsible for the 2 or 3 duplicates we received as soon as charset-normalizer released before it could be tested or fixed.

[nateprewitt]

What are the plans for the next release? Is it going to happen within days or months? Or is it still waiting for some blockers?

Requests has released twice yearly usually December and June since 2018, except for exceptional circumstances. You can find the full list of open issues attached to the milestone for 2.29.0.

As Ian has stated this is all easily discoverable through the tools GitHub provides to manage projects. It's linked from the original PR you've provided as well.

I think there's some confusion about being dismissive v. needing to reiterate the same thing repeatedly. We've answered all of the above questions previously but there's an entitlement that we provide this information to you directly instead of taking the time to do minimal research. This isn't scalable to the millions of people using Requests, so responses are often curt.

We'll plan to do the next release in the coming week or after the new year, as is the normal release cadence. We're currently waiting to resolve final blockers for urllib3 2.0's release.