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 vstinner
Recipients corona10, nascheme, petdance, serhiy.storchaka, shihai1991, steve.dower, vstinner
Date 2020-02-18.13:50:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> If we can keep functions that don't modify the object to accept const PyObject* it will help make things safer in the long run.

In my experience, trying to add "const" is quite painful, since the "const" has to be propagated to all functions called by the modified function. Python never used "const" with "PyObject*" because they are *so many* functions which really modify objects on purpose.

I don't see how adding "const" would help this issue "Make PyObject an opaque structure in the limited C API". If you consider that something should be changed, please open a *separated* issue.
Date User Action Args
2020-02-18 13:50:56vstinnersetrecipients: + vstinner, nascheme, serhiy.storchaka, steve.dower, corona10, shihai1991, petdance
2020-02-18 13:50:56vstinnersetmessageid: <>
2020-02-18 13:50:56vstinnerlinkissue39573 messages
2020-02-18 13:50:56vstinnercreate