Hi Robin,
The correct range requirements are mandatory from beta 2. There will be 2
more betas after beta 3: beta4 and beta5.
Please, check out the release announcement for beta3.
Cheers,
Pablo Galindo Salgado
On Fri, 3 Jun 2022, 09:56 Robin Becker, wrote:
> On 01/06/2022 16:58, Pablo Galindo
On 01/06/2022 16:58, Pablo Galindo Salgado wrote:
Update: we have decided to release Python 3.11.0b3. Let's hope this one is
free of the curse :)
Hi I hade a couple of failures related to the compile failure for ASTs with
wrongly ranged start-end attributes.
After spending a while so
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 f
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 sp
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.
On Tue, 31 May 2022 at 23:39, Pablo Galindo Salgado
wrote:
> > Wouldn't it be more practical to bite the bullet and release b3
> immediately with this fix?
>
> I
> 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 a
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 th
I have added a small note in the release announcements. Thanks for raising
this with us!
On Wed, 1 Jun 2022 at 00:13, Jean Abou Samra wrote:
>
>
> Le 01/06/2022 à 00:02, Pablo Galindo Salgado a écrit :
> > You may be able to work around this issue by preventing pytest to
> > rewrite the assert s
Le 01/06/2022 à 00:02, Pablo Galindo Salgado a écrit :
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.
Thank you! That did the trick. Worth mentioning in
Hi,
Le 31/05/2022 à 15:31, Pablo Galindo Salgado a écrit :
We **strongly encourage** maintainers of third-party Python projects
to **test with 3.11** during the beta phase and report issues found to
[the Python bug tracker](https://github.com/python/cpython/issues) as
soon as possible.
I j
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.
On Tue, 31 May 2022 at 23:57, Jean Abou Samra wrote:
> Hi,
>
>
> Le 31/05/2022 à 15:31, Pablo Galindo Salgado
11 matches
Mail list logo
