[Python-Dev] PEP 575 (Unifying function/method classes) update: limit? (original) (raw)
Paddy McCarthy paddy3118 at gmail.com
Thu May 10 03:11:37 EDT 2018
- Previous message (by thread): [Python-Dev] PEP 575 (Unifying function/method classes) update
- Next message (by thread): [Python-Dev] PEP 575 (Unifying function/method classes) update
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, 8 May 2018, 16:33 Jeroen Demeyer, <J.Demeyer at ugent.be> wrote:
On 2018-05-06 09:35, Nick Coghlan wrote: > Thanks for this update Jeroen! If it doesn't come up otherwise, I'll try > to claim one of the lightning talk slots at the Language Summit to > discuss this with folks in person :)
Sounds great! I'd love to hear what people think. As an example of how the new functionality of PEP 575 can be used, I changed functools.lrucache to implement the lrucachewrapper class as subclass of basefunction. I added this to the reference implementation https://github.com/jdemeyer/cpython/tree/pep575
It is not so much the use, but the abuse that I am worried about. If their was a way to limit the complexity of expression allowed around the use of the name assigned to by :=, then that would be a start. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20180510/58c18815/attachment.html>
- Previous message (by thread): [Python-Dev] PEP 575 (Unifying function/method classes) update
- Next message (by thread): [Python-Dev] PEP 575 (Unifying function/method classes) update
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]