# PEP 554: Multiple Interpreters in the Stdlib

**URL:** <https://discuss.python.org/t/pep-554-multiple-interpreters-in-the-stdlib/24855>\
**Category:** PEPs\
**Created:** [March 14, 2023, 11:29pm UTC](https://discuss.python.org/t/pep-554-multiple-interpreters-in-the-stdlib/24855 "2023-03-14T23:29:00Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![steve.dower](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/steve.dower/32/56_2.png) [@steve.dower](https://discuss.python.org/u/steve.dower)\
**Post date:** [April 24, 2023, 12:02pm UTC](https://discuss.python.org/t/pep-554-multiple-interpreters-in-the-stdlib/24855/12 "2023-04-24T12:02:18Z")

</div>

> [@jsbueno](#):
>
> My object uses a PyMemoryView\_FromMemory call - maybe this PEP could preview a native emoryview subclass that would could be instantiated in Python from the pointer to buffer-implementing object (the one obtainable with the “id” call - I had to use the pointer given by bufffer.buf in C), and that, most importantly, “closes” automatically when the “remote” parent object is de-referred.

Something like this is the eventual goal (at least last time I chatted with Eric about it), but we didn’t want to preempt the design, or hold up the building blocks on it.

Any design that gains wide usage and proves itself has got a very good chance of moving into the standard library one day (or being blatantly copied by a stdlib implementation 😉 ).

---

_[View the full topic](https://discuss.python.org/t/pep-554-multiple-interpreters-in-the-stdlib/24855)._