I’ve seen a few people in this thread proposing a new tool to automatically
update deprecations but I believe it already exists: pyupgrade. Looking
over its fixes once again, I don’t think it covers any of the original
three deprecations (maybe someone could open a PR?), but it does cover a
lot inc
On 11/17/2021 5:47 PM, Barry Warsaw wrote:
Does PEP 563 or 649 satisfy static and dynamic typing needs?
In the interest of full transparency, we want to let the Python community know
that the Steering Council continues to discuss PEP 563 (Postponed Evaluation of
Annotations) and PEP 649 (Defer
Hello Ethan,
The Steering Council has been discussing PEP 663 (Improving and Standardizing
Enum str(), repr(), and format() behaviors), for the last few weeks. We want
to thank you for your work on this PEP and your continued work on enums in the
standard library.
Upon further consideration,
Does PEP 563 or 649 satisfy static and dynamic typing needs?
In the interest of full transparency, we want to let the Python community know
that the Steering Council continues to discuss PEP 563 (Postponed Evaluation of
Annotations) and PEP 649 (Deferred Evaluation Of Annotations Using
Descript
Hello Mark, Matthew, Pradeep, Vincent, and Guido,
The Python Steering Council discussed the latest version of PEP 646 (Variadic
Generics) at our last meeting, and have unanimously decided to accept the PEP.
Congratulations!
We want to specifically mention that we appreciate the way you called
Hi Barry,
That's fantastic news!
Somewhat embarrassingly, on typing-sig we're still discussing one or two
final tweaks. In particular, the PEP as accepted forbids a certain
construct (passing a tuple of indefinite length to a function using `*args:
*Ts`) that after all we may actually want to all
