[Python-Dev] Should I postpone PEP 558 (locals() semantics) to Python 3.9? (original) (raw)
Nick Coghlan ncoghlan at gmail.com
Fri May 31 06:20:59 EDT 2019
- Previous message (by thread): [Python-Dev] Should I postpone PEP 558 (locals() semantics) to Python 3.9?
- Next message (by thread): [Python-Dev] Should I postpone PEP 558 (locals() semantics) to Python 3.9?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri., 31 May 2019, 6:34 pm Nathaniel Smith, <njs at pobox.com> wrote:
I wouldn't mind having a little more breathing room. It's frustrating to miss the train, but these bugs are several decades old so I guess nothing terrible will happen if their fixes get delayed to 3.9.
And I could put that extra time to good use, as starting to flesh out the proxy implementation showed that we're missing a lot of scaffolding to help make it easier to define new low level mapping types without duplicating a lot of code.
I'll update the PEP headers accordingly.
Cheers, Nick.
-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20190531/7f9be1ea/attachment.html>
- Previous message (by thread): [Python-Dev] Should I postpone PEP 558 (locals() semantics) to Python 3.9?
- Next message (by thread): [Python-Dev] Should I postpone PEP 558 (locals() semantics) to Python 3.9?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]