Message 287758 - Python tracker

➜

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	lemburg
Recipients	lemburg, mark.dickinson, methane, serhiy.storchaka, vstinner
Date	2017-02-14.10:09:52
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1487066993.17.0.129702033196.issue29548@psf.upfronthosting.co.za>
In-reply-to

Content
Looking through Python's history, it's interesting that PyObject_Call() did apply the args == NULL checks up until Python 2.1. In Python 2.2 this was replaced by a direct call to tp_call, without the checks. However, the tp_call slots don't do this check as you can see in function_call() of function objects. And indeed, the documentation of PyObject_Call() was changed in that version as well to disallow args == NULL.

Looking through Python's history, it's interesting that PyObject_Call() did apply the args == NULL checks up until Python 2.1.

In Python 2.2 this was replaced by a direct call to tp_call, without the checks. However, the tp_call slots don't do this check as you can see in function_call() of function objects. And indeed, the documentation of PyObject_Call() was changed in that version as well to disallow args == NULL.

History
Date	User	Action	Args
2017-02-14 10:09:53	lemburg	set	recipients: + lemburg, mark.dickinson, vstinner, methane, serhiy.storchaka
2017-02-14 10:09:53	lemburg	set	messageid: <1487066993.17.0.129702033196.issue29548@psf.upfronthosting.co.za>
2017-02-14 10:09:53	lemburg	link	issue29548 messages
2017-02-14 10:09:52	lemburg	create