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 josh.r
Recipients josh.r, vstinner
Date 2016-04-21.18:42:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1461264128.08.0.750983302622.issue26820@psf.upfronthosting.co.za>
In-reply-to
Content
The motivation for this change was Mr. STINNER's comment on #26814 ( https://bugs.python.org/issue26814#msg263923 ), where he mentioned the weirdness of PyObject_CallFunction and friends, which complicates the implementation of PyObject_FastCall and alerted me to a second case ( #21209 ) in which this silent fix up has caused confusing issues in CPython (I filed #26478 so I recognized the issue).

If this fix could be made, it might be possible to eventually make the check for non-tuple arguments a debug build only check (or a check only on public APIs), allowing the implementation in release mode and/or internal APIs to avoid the work involved in constantly checking for and performing this workaround to fix doc violating code, and possible simplify PyObject_FastCall by removing the corner case.
History
Date User Action Args
2016-04-21 18:42:08josh.rsetrecipients: + josh.r, vstinner
2016-04-21 18:42:08josh.rsetmessageid: <1461264128.08.0.750983302622.issue26820@psf.upfronthosting.co.za>
2016-04-21 18:42:08josh.rlinkissue26820 messages
2016-04-21 18:42:07josh.rcreate