[Tim, thrashing]
> ...
> So it's clearly expecting a tuple. But its entry in the builtin_methods[]
> table is:
>
> {"len", builtin_len, 1, len_doc},
>
> That is, it says nothing about the calling convention.
Oops, it does, using a hardcoded 1 instead of the METH_VARARGS #define. So
that explains that.
Next question: why isn't builtin_len using METH_OLDARGS instead? Is there
some advantage to using METH_VARARGS in this case? This gets back to what
these #defines are intended to *mean*, and I still haven't figured that out.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4