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 Akos Kiss
Recipients Akos Kiss, ammar2, eric.smith, rhettinger, serhiy.storchaka, vstinner
Date 2020-02-20.16:30:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1582216209.62.0.920728055343.issue39694@roundup.psfhosted.org>
In-reply-to
Content
I couldn't find any discussion in the language reference about fundamental differences between calls to built-in functions and user-defined functions. (I tried to read Sections 6.3.4. "Calls" and 8.6. "Function definitions" carefully.) Until now I had the impression that built-in and user-defined functions should be as similar as possible.

BTW, a user-defined function can also implement support for unused/excess keyword arguments (or arguments used on-demand): it only has to add **kwargs at the end of its signature. And that's exactly how the documentation specifies the signature of format: str.format(*args, **kwargs). That API documentation signals (to me at least) that this function should be called just like any other function that has a (*args, **kwargs) signature, be it built-in of user-defined.
History
Date User Action Args
2020-02-20 16:30:09Akos Kisssetrecipients: + Akos Kiss, rhettinger, vstinner, eric.smith, serhiy.storchaka, ammar2
2020-02-20 16:30:09Akos Kisssetmessageid: <1582216209.62.0.920728055343.issue39694@roundup.psfhosted.org>
2020-02-20 16:30:09Akos Kisslinkissue39694 messages
2020-02-20 16:30:09Akos Kisscreate