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
_
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
ACTIVITY SUMMARY (2019-11-15 - 2019-11-22)
Python tracker at https://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue.
Do NOT respond to this message.
Issues counts and deltas:
open7171 (+23)
closed 43475 (+57)
total 50646 (+80)
Open issues wi
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
I did a quick hack up of letting configs control what command line options
were available. I'm not sure y'all wanted it but here it is. I'm happy to
take suggestions including tossing the whole thing and chalking it up to
experience.
It's lightly tested with the syslog implementation from the spy
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
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
