> 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 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. For testing at fedora, you can temporarily patch beta2 and include this commit:

https://github.com/python/cpython/commit/b425d887aa51c8e7900b08cb8df457f450f6fbfd

On Wed, 1 Jun 2022 at 00:19, Miro Hrončok <mhroncok@redhat.com> wrote:

On 01. 06. 22 0:02, Pablo Galindo Salgado wrote:
> You may be able to work around this issue by preventing pytest to rewrite the
> assert statements by adding `--assert=plain` to the command line invocation
> until we have beta 3 next month.

That's possibly dozens---if not hundreds---of CI setups that would require a
temporary hack in order to be able to continue testing with Python 3.11. It's
wonderful that they can and many already do that now. Wouldn't it be more
practical to bite the bullet and release b3 immediately with this fix?

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok