> 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
On 09/13/18 23:34, Neil Schemenauer wrote:
On 2018-09-04, Eddie Elizondo wrote:
Solution:
* Fix the implementation of PyStructSequence_NewType:
The best solution would be to fix the implementation of this
function. This can easily be done by dynamically creating a
PyType_Spec and calling
On 2018-09-04, Eddie Elizondo wrote:
> Solution:
>
> * Fix the implementation of PyStructSequence_NewType:
>
> The best solution would be to fix the implementation of this
> function. This can easily be done by dynamically creating a
> PyType_Spec and calling PyType_FromSpec
Hello Eddie,
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,
