proposal, change self. to .

[Nick Dumas]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

It's also worth noting that you can use a different name for the object
that represents your class. If you did def __init__(foo):pass, then you
would be able to access the class's objects with foo.objectname. Using
self is simply the recommended standard.

Heiko Wundram wrote:
> Am 03.08.2008, 12:51 Uhr, schrieb Equand <equand at gmail.com>:
>> how about changing the precious self. to .
>> imagine
>>
>> self.update()
>>
>> .update()
>>
>> simple right?
> 
> What about:
> 
> class x:
> 
>      def x(self,ob):
>          ob.doSomethingWith(self)
> 
> ? Not so simple anymore, isn't it? If you're not trolling, there's
> hundreds of reasons why the explicit self is as it is, and it's not going
> to go away, just as a thread that produced immense amounts of response
> demonstrated around a week ago. Read that, and rethink.
> 
> --- Heiko.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkiVqEcACgkQLMI5fndAv9j8KgCgmS2e+bTOT+sUPLYhtHBOVlyq
kxwAn028YSOGYGB4RyHZxYq6n4+tsSd+
=vH9d
-----END PGP SIGNATURE-----