René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Expose _PyInterpreterFrame_GetLine in the private API","articleBody":"In 3.11 we are using now an opaque pointer to `_PyInterpreterFrame` in the eval function. The problem is that for PEP 523's APIs, we changed the type of `_PyFrameEvalFunction` to be `PyObject *(*_PyFrameEvalFunction)(PyThreadState *tstate, _PyInterpreterFrame *frame, int throwflag)` but there is no way to do anything with `_PyInterpreterFrame` because is opaque. Even if the extension defines `PY_BUILD_CORE` the symbols are not exposed in the executable/libpython, which means that including the headers is insufficient.\r\n\r\nThis is a problem because it really limits what users of PEP 523 can do with the frame object that they receive, even if is opaque. Most profilers using PEP 523 API do it for speed reasons and the only thing they need is to get the line number, but that is now impossible because the pointer is opaque and we don't offer any exposed APIs.\n\n\u003c!-- gh-linked-prs --\u003e\n### Linked PRs\n* gh-96849\n* gh-104211\n* gh-107188\n* gh-107195\n\u003c!-- /gh-linked-prs --\u003e\n","author":{"url":"https://github.com/pablogsal","@type":"Person","name":"pablogsal"},"datePublished":"2022-09-13T16:52:05.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":13},"url":"https://github.com/96803/cpython/issues/96803"}