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.
On Thu, May 30, 2019 at 4:23 PM Nick Coghlan <ncogh...@gmail.com> wrote: > > Hi folks, > > The reference implementation for PEP 558 (my attempt to fix the interaction > between tracing functions and closure variables) is currently segfaulting > somewhere deep in the garbage collector, and I've found that there's an issue > with the PyEval_GetLocals() API returning a borrowed reference that means I > need to tweak the proposed C API a bit such that PyEval_GetLocals() returns > the proxy at function scope, and we add a new PyEval_GetPyLocals() that > matches the locals() builtin. > > I don't *want* to postpone this to Python 3.9, but there turned out to be > more remaining work than I thought there was to get this ready for inclusion > in beta 1. > > I'll try to get the C API design details sorted today, but the segfault is > mystifying me, and prevents the option of putting the core implementation in > place for b1, and tidying up the documentation and comments for b2. > > Cheers, > Nick. > _______________________________________________ > Python-Dev mailing list > Python-Dev@python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > https://mail.python.org/mailman/options/python-dev/njs%40pobox.com -- Nathaniel J. Smith -- https://vorpus.org _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
