Le 01/06/2022 à 19:11, Miro Hrončok a écrit :
On 01. 06. 22 17:47, Pablo Galindo Salgado wrote:
Hi everyone,
Due to a known incompatibility with pytest and the previous beta
release (Python 3.11.0b2) and after
some deliberation, me and the rest of the release team have decided
to do an
On 01. 06. 22 17:47, Pablo Galindo Salgado wrote:
Hi everyone,
Due to a known incompatibility with pytest and the previous beta release
(Python 3.11.0b2) and after
some deliberation, me and the rest of the release team have decided to do an
expedited release of
Python 3.11.0b3 so the
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 wrote:
> On 01. 06. 22 0:39, Pablo Galindo Salgado wrote:
> > > Wouldn't it be more practical to bite the bullet and release b3
> immediately
> > with this
Hi everyone,
Due to a known incompatibility with pytest and the previous beta release
(Python 3.11.0b2) and after
some deliberation, me and the rest of the release team have decided to do
an expedited release of
Python 3.11.0b3 so the community can continue testing their packages with
pytest and
I understand issues and welcome any discussions. For that matter I do not
rush to conclusions. I am not expert in C and Python as the rest of the
folks on this list
but I am pretty good with Python itself. I just suggested naming to be as
simple as possible for all relevant API's including full
Sasha Kacanski writes:
> Why you don't simplify with api A,B,C and forth and then follows
> explanation ofr what is stable, unstable, semi... So forth
This is exactly what they're hammering out. It's not easy for several
reasons, chief of which is that in each case the boundary is a
On 01. 06. 22 0:39, Pablo Galindo Salgado 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 this is not practical but I
am not fully convinced about the balance. Beta 3 is in one month and
