Victor Stinner victor.stinner at gmail.com
Wed Aug 31 02:18:12 EDT 2016

• Previous message (by thread): [Python-Dev] Update on PEP 523 and adding a co_extra field to code objects
• Next message (by thread): [Python-Dev] Lib/http/client.py: could it return an OSError with the current response?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

The PEP 445, C API for malloc, allows to plug multiple wrappers and each
wrapper has its own "void* context" data. When you register a new wrapper,
you store the current context and function to later chain it.

See the hooks example:
https://www.python.org/dev/peps/pep-0445/#use-case-3-setup-hooks-on-memory-block-allocators

Since the PEP 523 also adds a function, would it be possible to somehow
design a mecanism to "chain wrappers"?

I know that the PEP 523 has a different design, so maybe it's not possible.

For example, the context can be passed to PyFrameEvalFunction. In this
case, each project would have to register its own eval function, including
vmprof. I don't know if it makes sense for vmprof to modify the behaviour
at runtime (add a C frame per Python eval frame).

Victor
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20160831/b8edab90/attachment.html>

---

• Previous message (by thread): [Python-Dev] Update on PEP 523 and adding a co_extra field to code objects
• Next message (by thread): [Python-Dev] Lib/http/client.py: could it return an OSError with the current response?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list