Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #80213

Re: [Python-Dev] Dinamically set __call__ method

Date 2014-11-04 10:23 -0800
From Ethan Furman <ethan@stoneleaf.us>
Subject Re: [Python-Dev] Dinamically set __call__ method
References <CAF0TK51TKs+tw=u_rzrWVeSsDK7cOBt1Gcvq_izLfMObuDYNig@mail.gmail.com>
Newsgroups comp.lang.python
Message-ID <mailman.15460.1415125440.18130.python-list@python.org> (permalink)

Show all headers | View raw


This list is for the development _of_ Python, not development _with_ Python.

Try asking on Python List.

(forwarding...)

On 11/04/2014 08:52 AM, Roberto Martínez wrote:
>
> I am trying to replace dinamically the __call__ method of an object using setattr.
> Example:
>
> $ cat testcall.py
> class A:
>      def __init__(self):
>          setattr(self, '__call__', self.newcall)
>
>      def __call__(self):
>          print("OLD")
>
>      def newcall(self):
>          print("NEW")
>
> a=A()
> a()
>
> I expect to get "NEW" instead of "OLD", but in Python 3.4 I get "OLD".
>
> $ python2.7 testcall.py
> NEW
> $ python3.4 testcall.py
> OLD
>
> I have a few questions:
>
> - Is this an expected behavior?
> - Is possible to replace __call__ dinamically in Python 3? How?

In 2.7 that would be a classic class, about which I know little.

In 3.x you have a new class, one which inherits from 'object'.  When you replace __call__ you need to replace it the 
class, not on the instance:

   setattr(__self__.__class__, self.newcall)

--
~Ethan~

Back to comp.lang.python | Previous | Next — Next in thread | Find similar | Unroll thread


Thread

Re: [Python-Dev] Dinamically set __call__ method Ethan Furman <ethan@stoneleaf.us> - 2014-11-04 10:23 -0800
  Re: [Python-Dev] Dinamically set __call__ method alex23 <wuwei23@gmail.com> - 2014-11-05 15:28 +1000

csiph-web