Hey Inada, thanks for the feedback
> Generally speaking, fork is a legacy API. It is too difficult to know which
> library is fork-safe, even for stdlibs.
Yes, this is something that Instagram has to go into great lengths to make sure
that we get the entire execution into a state where it's saf
I've just updated the original Immortal Instances PR with a bunch of tricks
that I used to achieve as much performance parity as possible:
https://github.com/python/cpython/pull/19474 . You can see the details along
with some benchmarks in the PR itself.
This should address a bunch of the origi
Copy on writes are a big problem in large Python application that rely on
multiple processes sharing the same memory.
I just sent out a patch introduces Immortal Instances which allows the user to
bypass reference counting on specific objects to avoid CoW on forked processes.
This has helped in
Hi everyone,
I found a bug in subtype_dealloc causing segfaults when used with C heap types.
Given that it modifies the deallocation routine of every instance, I thought it
was important to surface this in here as well. Also worth noting, this blocks
the adoption of PEP384 in C Extension modul
s a custom tp_dealloc and it’s not decrefing the type. The
fix here is that a custom tp_dealloc should ALWAYS decref the type.
Open to feedback/discussion so feel free to reply if you have any questions!
- Eddie Elizondo
___
Python-Dev mailing list
Python-Dev@
> We have to assess how 3rd party extension modules would be affected
> by this change.
This change is fully compatible with 3rd party extensions.
The current change to InitType2 is only refactoring, there is no logic change
there so that API remains unchanged.
Also, there should not be any insta
PEP-384 talks about defining a Stable ABI by making PyTypeObject opaque. Thus,
banning the use of static PyTypeObjects.
Specifically, I’d like to focus on those static PyTypeObjects that are
initialized as StructSequences. As of today, there are 14 instances of these
types (in timemodule.c, pos
Hi everyone,
Sorry for the delay - I finally sent out a patch:
https://bugs.python.org/issue34522.
Also, I'm +1 for modifying all extension modules to use PyType_FromSpec! I
might lend a hand to start moving them :)
- Eddie
On 8/13/18, 6:02 AM, "Erik Bray" wrote:
On Fri, Aug 10, 2018
Background:
Through the implementation of an alternate runtime I've been poking around some
of the class initialization routines and I found out that there was a subtle
bug with PyType_Ready and the header initializer PyVarObject_HEAD_INIT.
Looking through the codebase, I couldn't really find an
