X Tutup

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 Antony.Lee
Recipients Antony.Lee, brett.cannon, hrik2001, mark.dickinson, rhettinger, vstinner
Date 2021-08-30.17:34:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1630344880.61.0.636395665694.issue44019@roundup.psfhosted.org>
In-reply-to
Content
> I'm not convinced that operator.caller() would be useful to me.

To be clear, as noted above, I have realized that the semantics I initially proposed (now known as "caller") are not particularly useful; the semantics I am proposing (and implementing in the linked PR) are `call(f, *args, **kwargs) == f(*args, **kwargs)`.

> I don't see how operator.caller() implements an existing "intrinsic operators of Python".

Agreed; on the other hand function calling is much more intrinsic(?!)

> Can't you use functools.partial() for that?

How do you propose to do that?  Perhaps I am missing an easy solution...
History
Date User Action Args
2021-08-30 17:34:40Antony.Leesetrecipients: + Antony.Lee, brett.cannon, rhettinger, mark.dickinson, vstinner, hrik2001
2021-08-30 17:34:40Antony.Leesetmessageid: <1630344880.61.0.636395665694.issue44019@roundup.psfhosted.org>
2021-08-30 17:34:40Antony.Leelinkissue44019 messages
2021-08-30 17:34:40Antony.Leecreate
X Tutup