Update: we have decided to release Python 3.11.0b3. Let's hope this one is free of the curse :) On Wed, 1 Jun 2022 at 07:38, Miro Hrončok <mhroncok@redhat.com> wrote:
Wouldn't it be more practical to bite the bullet and release b3 immediately with this fix?
I sympathize with the sentiment and I am sorry that
On 01. 06. 22 0:39, Pablo Galindo Salgado wrote: this is not practical but I
am not fully convinced about the balance. Beta 3 is in one month and spinning an entire release is a multi-hour process for at least 3 people. I will discuss this with the release team but is unlikely.
Understood. It's always a balance.
For testing at fedora, you can temporarily patch beta2 and include this commit:
Thanks. We already do that, my comment was motivated by the majority of upstream CI which do not use Fedora's Python 3.11 (yet?).
Just for the heads up: I have sent an email to the release team and we are considering the proposal. Thanks for raising this with us.
Awesome, thanks again.
-- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok