[issue28349] Issues with PyMemberDef flags

Alexander Belopolsky added the comment: There is also #24065 ("Outdated *_RESTRICTED flags in structmember.h") which I think should be folded into #2897. -- ___ Python tracker _

[issue28349] Issues with PyMemberDef flags

Serhiy Storchaka added the comment: Ah this is a duplicate of issue24065! -- resolution: -> duplicate stage: needs patch -> resolved status: open -> closed superseder: include structmember.h in Python.h -> Outdated *_RESTRICTED flags in structmember.h _

[issue28349] Issues with PyMemberDef flags

Alexander Belopolsky added the comment: Serhiy, while I see that you've raised some additional issues here, let's keep the discussion related to Include/structmember.h in one place. I would not mind adding additional affected versions there. -- nosy: +belopolsky _

[issue28349] Issues with PyMemberDef flags

Serhiy Storchaka added the comment: We still should correct the documentation in 2.7 and 3.x. -- resolution: duplicate -> stage: resolved -> needs patch status: closed -> open ___ Python tracker __

[issue28349] Issues with PyMemberDef flags

Changes by Alexander Belopolsky : -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> include structmember.h in Python.h ___ Python tracker __

[issue28349] Issues with PyMemberDef flags

Serhiy Storchaka added the comment: The latter issue is a duplicate of issue2897. -- ___ Python tracker ___ ___ Python-bugs-list maili

[issue28349] Issues with PyMemberDef flags

New submission from Serhiy Storchaka: As documented in Doc/extending/newtypes.rst, the flags field of PyMemberDef must be bitwise-or-ed combination of flag constants READONLY, READ_RESTRICTED, WRITE_RESTRICTED and RESTRICTED. There are problems with this: 1. Actually WRITE_RESTRICTED was renam