Hi all

I'm one of the Hypothesis core developers, for which this will be very useful indeed - we have several decorators which modify the signature of the wrapped function, and currently we just check the return types.

I am also responsible for the `from_type()` strategy, which does runtime inspection of types (or type-annotated functions, classes, methods, ...) and works out how to call them.  So I would really appreciate it if the implementation of ParameterSpecifications and the various type operators preserved enough information at runtime to reconstruct the semantics of that use!  
(Contrast TypedDict with optional keys: https://bugs.python.org/issue38834, fixed for 3.9). 

Happy to review things, draft our implementation against a prototype, etc. - just let me know.

Best wishes from a continent literally on fire,

On Fri, 20 Dec 2019 at 09:56, Mark Mendoza <mendoza.mark.a@gmail.com> wrote:
Hi All,
I want to announce the submission of a new typing PEP, for ParameterSpecifications (https://github.com/python/peps/pull/1259).  We discussed this concept at the last typing summit (presentation can be found here https://github.com/facebook/pyre-check/blob/master/docs/Variadic_Type_Variables_for_Decorators_and_Tensors.pdf), and there seemed to be general consensus on the utility of this idea, and the appropriateness of the particular solution.

One note that I know there was some disagreement on was the name for the feature itself, with some folks preferring ArgSpec.  I wrote up a brief note in the PEP itself why we're not as big fans of that name, but I'd love to hear all of your opinions on this issue, as well as on anything else in the PEP.

Mark Mendoza
Typing-sig mailing list -- typing-sig@python.org
To unsubscribe send an email to typing-sig-leave@python.org