Should we delegate typing PEPs to a separate body?

[gvanrossum]

Once the beta 1 is on its way, maybe the SC would like to lighten its load by permanently delegating PEPs related to typing to another body, similar to the way it's done for packaging PEPs.

PEPs proposing new syntax would still have to be approved by the SC, but PEPs that just propose a new "special form" to be added to the typing module would just have to be approved by a newly formed body in which representatives of the major static type checkers are present (I think that's PyCharm, mypy, pytype, pyre, and pyright).

Thoughts?

[gpshead]

My first reaction is that this might not be a great idea. With people concerned over growing typing topics impact on the broader language, having typing PEP decisions default to happening outside of the main council could lead to more issues? I think a Steering Council delegate system for these makes sense. Not entirely removing the steering council from the process. I'm envisioning this being the council saying "yes, we trust this specific set of people to unanimously decide this PEP under constraints X/Y/Z". Also, from recent threads, a separate body for typing should include more than just the static folks. Represent use of runtime typing (pydantic?) and possibly even things we wish could play better with typing (attrs? ORMs?). A set of delegates and the body your proposing may wind up being the same much of the time. Food for thought / My two cents, -Greg

…

On Fri, Apr 23, 2021, 9:21 PM Guido van Rossum ***@***.***> wrote: Once the beta 1 is on its way, maybe the SC would like to lighten its load by permanently delegating PEPs related to typing to another body, similar to the way it's done for packaging PEPs. PEPs proposing new syntax would still have to be approved by the SC, but PEPs that just propose a new "special form" to be added to the typing module would just have to be approved by a newly formed body in which representatives of the major static type checkers are present (I think that's PyCharm, mypy, pytype, pyre, and pyright). Thoughts? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#64>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAQXC6W2NQQ3FUXUSBDKYTTKJBLDANCNFSM43PXDE4Q> .

[bskinn]

As a potential additional project from which to draw a member of a typing body: numpy stakeholders have been discussing how to add types for a few years now.

[warsaw]

As per this message the SC will continue to reserve the final decision making process for typing PEP, although individual PEPs may be delegated on a case-by-case basis, as per existing policy.