➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Matthias Braun
Recipients Arfrever, Matthias Braun, belopolsky, benjamin.peterson, berker.peksag, docs@python, georg.brandl, herzbube, loewis, matrixise, rhettinger, serhiy.storchaka, skip.montanaro, vstinner
Date 2020-05-27.15:54:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1590594873.67.0.741365374673.issue2897@roundup.psfhosted.org>
In-reply-to
Content 
> The issue title is misleading, it says "Deprecate structmember.h". Is the plan still to deprecate it? Or to make it usable in the limited C API? Please update the title.

As far as I understand it: The attached diff, moves the interesting declaration to `object.h` solving the limited API problem. And only leaves structmember.h around for backward compatibility for people using the "old" names `READONLY` or `RESTRICTED`. So in that sense it does deprecate structmember.h

But indeed I hijacked this issue with my complaints about the limited API which may not have been the original intention here, but they get solved nonetheless.
History
Date User Action Args
2020-05-27 15:54:33Matthias Braunsetrecipients: + Matthias Braun, loewis, skip.montanaro, georg.brandl, rhettinger, belopolsky, vstinner, benjamin.peterson, Arfrever, herzbube, docs@python, berker.peksag, serhiy.storchaka, matrixise
2020-05-27 15:54:33Matthias Braunsetmessageid: <1590594873.67.0.741365374673.issue2897@roundup.psfhosted.org>
2020-05-27 15:54:33Matthias Braunlinkissue2897 messages
2020-05-27 15:54:33Matthias Brauncreate