fwiw we added immortal objects to Pyston and haven't run into any issues
with it. The goal is a bit different: to eliminate common refcount
operations for performance, which we can do a bit more of because we have a
jit. And we don't mind if unaware code ends up changing the refcounts of
immortal
ACTIVITY SUMMARY (2021-12-10 - 2021-12-17)
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:
open7180 (-15)
closed 50665 (+93)
total 57845 (+78)
Open issues
On 16. 12. 21 20:24, Eric Snow wrote:
On Thu, Dec 16, 2021 at 10:54 AM Guido van Rossum wrote:
Eric has been looking into this. It's probably the only solution if we can't
get immutable objects.
Yep. I've investigated the following approach (for the objects
exposed in the public and
On 17. 12. 21 4:02, Jim J. Jewett wrote:
Petr Viktorin wrote:
In Python 3.11, Python still implements around 100 types as "static
types" which are not compatible with subinterpreters,
...
seems like changing it may break the C API *and* the stable ABI
If sub-interpreters each need their
