Release 3.12 wheels

[gaborbernat]

Is your feature request related to a problem?

No response

Describe the solution you'd like

New release with 3.12 wheels in it.

Describe alternatives you've considered

N.a.

Related component

Client

Additional context

No response

Code of Conduct

• I agree to follow the aio-libs Code of Conduct

[Dreamsorcerer]

Already covered in other issues. New releases are blocked on nodejs/llhttp#249

[frenck]

@Dreamsorcerer I'm not sure why all issues are closed, while they aren't solved?

Sure, I understand this is an upstream issue. But closing all reports as "resolved" while they are not; will not reduce the issue creation and tracking 😉

Maybe leave one open, so people actually see it when they go into the aiohttp issue tracker? (as in, I can imaging the Python 3.12 becoming a hotter needle the upcoming days).

../Frenck

[Dreamsorcerer]

Mainly because there is no work for us to do (tasks to support Python 3.12 have been done already), so it's not a task we need to track. It could be left open for others to see, but I'll probably forget to close it, as there will be no PR related to this issue.

Wheels are created automatically on releases, so there are no actions for us to take. It will automatically include wheels for all supported versions of Python whenever a new release is made, we don't need anyone to remind us to create wheels.

[layday]

Could a release be made from an older version of llhttp which does not exhibit this issue? Sent with [Proton Mail](https://proton.me/) secure email.

…

------- Original Message -------

On Tuesday, October 3rd, 2023 at 13:26, Sam Bull ***@***.***> wrote: Mainly because there is no work for us to do (tasks to support Python 3.12 have been done already), so it's not a task we need to track. It could be left open for others to see, but I'll probably forget to close it, as there will be no PR related to this issue. Wheels are created automatically on releases, so there are no actions for us to take. It will automatically include wheels for all supported versions of Python whenever a new release is made, we don't need anyone to remind us to create wheels. — Reply to this email directly, [view it on GitHub](#7639 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AHNRFWHG45WN3EBEX7DL2RLX5PR6XAVCNFSM6AAAAAA5P4CSR6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBUGY3TONBYGI). You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[Dreamsorcerer]

I'm afraid we have multiple issues hanging off the llhttp release, we can't go back. Once that regression is fixed in llhttp, we can quickly land the remaining bits we need and push out new releases.

[layday]

Ok, thanks for clarifying! Sent with [Proton Mail](https://proton.me/) secure email.

…

------- Original Message -------

On Tuesday, October 3rd, 2023 at 13:48, Sam Bull ***@***.***> wrote: I'm afraid we have multiple issues hanging off the llhttp release, we can't go back. Once that regression is fixed in llhttp, we can quickly land the remaining bits we need and push out new releases. — Reply to this email directly, [view it on GitHub](#7639 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AHNRFWFLDJX6VVZO6TISJJTX5PURNAVCNFSM6AAAAAA5P4CSR6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBUG4YTGNBTG4). You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[gaborbernat]

Wheels are created automatically on releases, so there are no actions for us to take. It will automatically include wheels for all supported versions of Python whenever a new release is made, we don't need anyone to remind us to create wheels.

Wouldn't this issue track that work though? When the upstream fix is ready cut a release...