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 jdemeyer
Recipients jdemeyer
Date 2018-07-30.11:56:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1532951795.78.0.56676864532.issue34280@psf.upfronthosting.co.za>
In-reply-to
Content
A C function with signature METH_NOARGS takes two arguments where the first is "self" and the second is guaranteed to be NULL. Given that this second argument really should never be used, I would like to drop the guarantee that the argument is NULL.

Concretely, I propose to change:

1. the documentation for METH_NOARGS

2. some functions in Modules/_io/bufferedio.c which actually do use the second argument of a METH_NOARGS function.

For the moment, the second argument is still NULL, but one is not supposed to rely on that.

The reason for this patch is that this second argument can be re-purposed in PEP 580 (and possibly PEP 573) to pass the function object.
History
Date User Action Args
2018-07-30 11:56:35jdemeyersetrecipients: + jdemeyer
2018-07-30 11:56:35jdemeyersetmessageid: <1532951795.78.0.56676864532.issue34280@psf.upfronthosting.co.za>
2018-07-30 11:56:35jdemeyerlinkissue34280 messages
2018-07-30 11:56:35jdemeyercreate