[Python-Dev] Re: [python-committers] PEP 563 and Python 3.10.

2021-04-21 Thread Anthony Baxter
While I have not been involved in the release process for like 15 years or more, I would like to point out that breaking changes mean the distros are less likely to ship them, and be less likely to trust updates. Trying to get RH to stop shipping 1.5.2 was a huge effort. Always, any time when

[Python-Dev] Re: [python-committers] PEP 563 and Python 3.10.

2021-04-20 Thread Samuel Colvin
This is great news! Thanks so much for hearing us and putting up with our last minute request. I'm sure we can find a solution that, while not perfect, can satisfy most of the people most of the time. Samuel ___ Python-Dev mailing list --

[Python-Dev] Re: [python-committers] PEP 563 and Python 3.10.

2021-04-20 Thread Sebastián Ramírez
This is amazing news! On behalf of the FastAPI/pydantic communities, thanks to the Steering Council, and everyone involved! I understand the big effort and commitment the Steering Council is making with this decision to support the pydantic and FastAPI communities (especially with our short

[Python-Dev] Re: [python-committers] PEP 563 and Python 3.10.

2021-04-20 Thread Guido van Rossum
Thanks to the Steering Council! You have the wisdom of Solomon. Rolling back the code that made PEP 563 the default behavior is the only sensible solution for 3.10. On Tue, Apr 20, 2021 at 11:58 AM Thomas Wouters wrote: > > (Starting a new thread so as not to derail any of the ongoing