PEP 718: Specify binding, parametrisation and overload interactions

[Gobot1234]

• Change is either:
  • [x] To a Draft PEP
  • [ ] To an Accepted or Final PEP, with Steering Council approval
  • [ ] To fix an editorial issue (markup, typo, link, header, etc)
• [x] PR title prefixed with PEP number (e.g. PEP 123: Summary of changes)

---

📚 Documentation preview 📚: https://pep-previews--4649.org.readthedocs.build/

[python-cla-bot[bot]]

All commit authors signed the Contributor License Agreement.

[Gobot1234]

Please can someone get the CLA bot to re-run? I'm not sure why it's requesting that email TBH. I've already signed it for my email [email protected]

[defjaf]

I don't think that the word "subscription" is being used correctly.

[hugovk]

Please can someone get the CLA bot to re-run? I'm not sure why it's requesting that email TBH. I've already signed it for my email [email protected]

You committed with your Git client configured with that email, see https://github.com/python/peps/pull/4649.patch

You also need to sign it with that.

[PabloRuizCuevas]

@Gobot1234 please if you need help don't hesitate to ask, I'm very interested on this feature and would be a pity to see it abandoned

[PabloRuizCuevas]

@JelleZijlstra Is there something I can do to move the needle on this PEP if the original author don't reply in a reasonable amount of time? like contributing to the writing of this PEP?

[JelleZijlstra]

@Gobot1234 is still around, I'd wait a bit longer. But this PEP has been sitting for a long time and as I've written on Discuss before, I personally have some reservations about it. If you're interested in renewing the discussion and addressing the concerns that have been raised about the PEP, you could work with James to improve the PEP, or even write your own replacement PEP.

[PabloRuizCuevas]

@JelleZijlstra I already wrote James in Discourse, in GitHub and in private offering my help on September, after that he did reappear (but didn't particularly requested my help).

Now is almost a month without updates from him and I would really like to see this coming in python 3.15 (if is approved etc ofc), given that he did vanish for more than a year last time (look in discourse the message of Guido on 7 May 2023), I think is reasonable to move forward with the PEP after almost a month without updates from him. So how can I do my own PEP replacement / edit this? Would I count with your sponsorship or the original one from @gvanrossum ?

thanks in advance

[JelleZijlstra]

You'd need a new sponsor. I'm not currently interested in sponsoring a version of this PEP, but another core dev might be.

[Gobot1234]

@PabloRuizCuevas I'm happy to review stuff for it and would happily add you as a co-author. I just don't really have the time/motivation to finish it as my usage of python is so little nowadays

[gvanrossum]

Alas, I can't take on sponsoring a new PEP either. But I will continue to fulfill my promises on the old one.

As a sponsor, I have to ask: what are the chances that the Typing Council will approve this PEP? That's the first and most important hurdle for typing PEPs.

[PabloRuizCuevas]

Ok I will help @Gobot1234 on finishing this one, @JelleZijlstra answering the concerns of Guido, and given that you belong to the typing council (right?), do you think that this PEP has any chance of being approved? If there is chances what would be the priority changes for me to make to advance on it. thanks in advance.

I guess the overload resolution as you already pointed out is one of them, right? anything else? I was planning to add other examples, motivations and ideas that were mentioned in discourse.

[JelleZijlstra]

I don't know what the Typing Council will decide but I wrote this last year: https://discuss.python.org/t/pep-718-subscriptable-functions/28457/38 and still feel the motivation for the PEP is weak.