Do we need offsetof?

@picnixz we do!

For one, because it is used in:

staticPyMemberDefxmlparse_members[]= {    {"intern",T_OBJECT, offsetof(xmlparseobject,intern),READONLY,NULL},    {NULL}};

For two, because it is added inde690f1, the source of the backport.

Hum. Why did add it? I think it was because my IDE complained at some point. Ok then.

@picnixz I need to correct me earlier statement: I got the commit wrong, it's actuallyf04bea4 and you didnot add that import there, it was already present inmain and 3.14 and 3.13. So the question now seems to be whether we want to add or not add that import in the backports targetting 3.12, 3.11 and 3.10. It's thecorrect header but then some other header must be already pulling it in or the code would not compile already prior to these backports. I'm good with dropping or keeping that new include — what would you prefer?

Try to reduce the diff as much as possible. If it works without the include then let's not add it. I think it would make better sense toremove it from 3.13 and 3.14 actually but I don't know if other files actually have an explicit or an implicit include policy...

Try to reduce the diff as much as possible. If it works without the include then let's not add it.

@picnixz okay, let me try…

I think it would make better sense toremove it from 3.13 and 3.14 actually but I don't know if other files actually have an explicit or an implicit include policy...

That I would have trouble supporting. Please don't.

@picnixz PS: I found…

Doc/c-api/structures.rst:   (You may need to ``#include <stddef.h>`` for :c:func:`!offsetof`.)

…and also…

Include/structmember.h:#include <stddef.h> /* For offsetof (not always provided by Python.h) */

in 3.12 code and that all of 3.10, 3.11, 3.12 havepyexpat.c includestructmember.h but 3.13, 3.14,main do not and so these seem to rightfully contain a dedicated#include <stddef.h> foroffsetof.

@picnixz okay, let me try…

Update: dropped from all of 3.10, 3.11, 3.12 backports by now.