A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2005-January/051130.html below:

[Python-Dev] Getting rid of unbound methods: patch available

[Python-Dev] Getting rid of unbound methods: patch available [Python-Dev] Getting rid of unbound methods: patch availableGlyph Lefkowitz glyph at divmod.com
Mon Jan 17 07:56:59 CET 2005
On Sun, 2005-01-16 at 22:12 -0800, Guido van Rossum wrote:

> What do people think? (My main motivation for this, as stated before,
> is that it adds complexity without much benefit.)

> ***************
> *** 331,339 ****
>   def test_im_class():
>       class C:
>           def foo(self): pass
> -     verify(C.foo.im_class is C)

^ Without this, as JP Calderone pointed out earlier, you can't serialize
unbound methods.  I wouldn't mind that so much, but you can't tell that
they're any different from regular functions until you're
*de*-serializing them.

In general I like the patch, but what is the rationale for removing
im_class from functions defined within classes?




More information about the Python-Dev mailing list

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