Message263930
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. |
|
Date |
User |
Action |
Args |
2016-04-21 18:42:08 | josh.r | set | recipients:
+ josh.r, vstinner |
2016-04-21 18:42:08 | josh.r | set | messageid: <1461264128.08.0.750983302622.issue26820@psf.upfronthosting.co.za> |
2016-04-21 18:42:08 | josh.r | link | issue26820 messages |
2016-04-21 18:42:07 | josh.r | create | |
|