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 abacabadabacaba
Recipients abacabadabacaba
Date 2015-10-21.18:53:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1445453619.22.0.222588930326.issue25454@psf.upfronthosting.co.za>
In-reply-to
Content
Currently, operator.methodcaller behaves like this:

    def methodcaller(name, *args, **kwargs):
        def caller(obj):
            return getattr(obj, name)(*args, **kwargs)
        return caller

That is, it is possible to supply arguments when the object is created but not during the call. I think that it will be more useful if it behaved like this:

    def methodcaller(name, *args, **kwargs):
        def caller(obj, *args2, **kwargs2):
            return getattr(obj, name)(*args, *args2, **kwargs, **kwargs2)
        return caller
History
Date User Action Args
2015-10-21 18:53:39abacabadabacabasetrecipients: + abacabadabacaba
2015-10-21 18:53:39abacabadabacabasetmessageid: <1445453619.22.0.222588930326.issue25454@psf.upfronthosting.co.za>
2015-10-21 18:53:39abacabadabacabalinkissue25454 messages
2015-10-21 18:53:39abacabadabacabacreate