[Python-Dev] Re: Stalemate on bringing back PEP 523 support into Python 3.8

2020-03-10 Thread Victor Stinner
Hi, I plan to merge my PR 17340 at the end of week to not miss Python 3.9 feature freeze deadline, unless someone speaks up and find a good reason to not merge this PR. The PR adds a public C API PyInterpreterState_SetEvalFrameFunc() and now pass tstate to the frame evaluation function. Please di

[Python-Dev] Re: Stalemate on bringing back PEP 523 support into Python 3.8

2019-11-25 Thread Brett Cannon
Victor Stinner wrote: > I modified "make install" to install internal header files, so it's > possible to use the internal C API in debuggers and profilers. For > example, to be able to inspect Python internals without having to call > functions (which might modify the Python internal state). I mad

[Python-Dev] Re: Stalemate on bringing back PEP 523 support into Python 3.8

2019-11-23 Thread Nick Coghlan
On Sat., 23 Nov. 2019, 9:46 am Gregory P. Smith, wrote: > > Anyways given there are workarounds to be able to continue using it in > 3.8.x, this doesn't feel 3.8.1 level *urgent*. It'd be good to document > the workarounds and 3.8 know issue in the PEP though as a addendum. > Aye, adding a Pyth

[Python-Dev] Re: Stalemate on bringing back PEP 523 support into Python 3.8

2019-11-22 Thread Gregory P. Smith
On Fri, Nov 22, 2019 at 10:10 AM Mark Shannon wrote: > Hi, > > On 21/11/2019 8:04 pm, Brett Cannon wrote: > > An unfortunate side-effect of making PyInterpreterState in Python 3.8 > opaque is it removed [PEP 523](https://www.python.org/dev/peps/pep-0523/) > support. https://www.python.org/dev/pep

[Python-Dev] Re: Stalemate on bringing back PEP 523 support into Python 3.8

2019-11-22 Thread Victor Stinner
I modified "make install" to install internal header files, so it's possible to use the internal C API in debuggers and profilers. For example, to be able to inspect Python internals without having to call functions (which might modify the Python internal state). I made this change to be able to mo

[Python-Dev] Re: Stalemate on bringing back PEP 523 support into Python 3.8

2019-11-22 Thread Eric Snow
I agree with Mark on "for now I propose that we do absolutely nothing". (I'll wait on a PEP for the rest of his points.) The capability of PEP 523 (swapping in a different PyEval_EvalFrame() impl.) is deep in the CPython runtime functionality. It is low-level, highly impactful, and there-be-drag

[Python-Dev] Re: Stalemate on bringing back PEP 523 support into Python 3.8

2019-11-22 Thread Mark Shannon
Hi, On 21/11/2019 8:04 pm, Brett Cannon wrote: An unfortunate side-effect of making PyInterpreterState in Python 3.8 opaque is it removed [PEP 523](https://www.python.org/dev/peps/pep-0523/) support. https://www.python.org/dev/peps/pep-0523/ was opened to try and fix this, but there seems to

[Python-Dev] Re: Stalemate on bringing back PEP 523 support into Python 3.8

2019-11-22 Thread Victor Stinner
I'm in favor of adding a public C API to get and set the frame evaluation function. API excluded from the limited API. I wrote https://github.com/python/cpython/pull/17340 to add such API to Python 3.8.1. For me, it's a Python 3.8.0 regression. Victor _

[Python-Dev] Re: Stalemate on bringing back PEP 523 support into Python 3.8

2019-11-21 Thread Ethan Smith
(Replying here since b.p.o doesn't seem to want to let me log in) I've used the PEP 523 API several times for multiple projects, from analyzing bytecode frequency (which probably could be done with other means) to inspecting type information from function calls. I could probably do such analysis a