«

Hello,

I'm a newbie Python user, a systems administrator - I've been trying
to switch from Perl to Python for administrative tasks - and one thing
I cannot understand so far is why I need the special 'self' (or anything
esle) argument in class method definitions. I might have missed an
explanation in the docs, a quick Google search did not help. Is there
somewhere on the web you could direct me to?

Thanks,

--
Grzegorz Staniak <>

Grzegorz Staniak wrote:
> Hello,
>
> I'm a newbie Python user, a systems administrator - I've been trying
> to switch from Perl to Python for administrative tasks - and one thing
> I cannot understand so far is why I need the special 'self' (or anything
> esle) argument in class method definitions. I might have missed an
> explanation in the docs, a quick Google search did not help. Is there
> somewhere on the web you could direct me to?

This entry of the Python FAQ:

http://www.python.org/doc/faq/genera...ions-and-calls

-- Gerhard

On Fri, Sep 05, 2003 at 01:58:41PM +0000, Grzegorz Staniak wrote:
> Hello,
>
> I'm a newbie Python user, a systems administrator - I've been trying
> to switch from Perl to Python for administrative tasks - and one thing
> I cannot understand so far is why I need the special 'self' (or anything
> esle) argument in class method definitions. I might have missed an
> explanation in the docs, a quick Google search did not help. Is there
> somewhere on the web you could direct me to?
>
> Thanks,
>
> --
> Grzegorz Staniak <>
> --
> http://mail.python.org/mailman/listinfo/python-list

The first argument in a class method is a reference to that class itself. It is
same as "this" pointer in c++ and java. Using this argument you can access the
class variables. ex:

class test:
def __init__(self,arg1,arg2): #this acts as class constructor
self.name=arg1
self.value=arg2


def changeName(self,newName): #here we change the name class variable
self.name=newName
..........and so on

regards
Vivek Kumar

Hi,

the answer is in python FAQ:

http://python.org/doc/faq/general.ht...ions-and-calls

--

=*= Lukasz Pankowski =*=

In article <>, John Roth wrote:

> Technically, it would be possible to make "self" a reserved
> word, and not have to put it in the method declaration.
> However, there are a lot of people who use something other than
> the word "self," so that would break existing code.

It would also make the language more complex and irregular.

--
Grant Edwards grante Yow! Could I have a drug
at overdose?
visi.com

"Grant Edwards" <> wrote in message
news:3f58a2bd$0$156$.. .
> In article <>, John Roth wrote:
>
> > Technically, it would be possible to make "self" a reserved
> > word, and not have to put it in the method declaration.
> > However, there are a lot of people who use something other than
> > the word "self," so that would break existing code.
>
> It would also make the language more complex and irregular.

How?

John Roth

>
> --
> Grant Edwards grante Yow! Could I have a
drug
> at overdose?
> visi.com

In article <>, John Roth wrote:
>
> "Grant Edwards" <> wrote in message
> news:3f58a2bd$0$156$.. .
>> In article <>, John Roth wrote:
>>
>> > Technically, it would be possible to make "self" a reserved
>> > word, and not have to put it in the method declaration.
>> > However, there are a lot of people who use something other than
>> > the word "self," so that would break existing code.
>>
>> It would also make the language more complex and irregular.
>
> How?

1) It would add a reserved word.

2) It would mean that there's some sort of difference between
a function and a method.

--
Grant Edwards grante Yow! I have a TINY BOWL in
at my HEAD
visi.com

wrote:
...
> The first argument in a class method is a reference to that class itself.

Yes, that's what defines CLASS methods (as opposed to ordinary, or
INSTANCE, methods). But the original poster was not asking about class
methods, and you're not giving any examples of them -- I only see
instance methods. I suspect a terminology problem -- you may be using
the term "class method" in a way that is totally inappropriate to
Python, where classes are first-level objects.


So -- in Python, you see...:

To make a class method you have to call on the classmethod built-in. E.g.:

class Example(object):

def instmeth(self): print 'Instance method of', self

def clasmeth(cls): print 'Class method of', cls
clasmeth = classmethod(clasmeth)

inst = Example()


Now you can call:

inst.instmeth()

or:

inst.clasmeth()
Example.clasmeth()

(both of these do exactly the same thing), but NOT:

Example.instmeth()

since an INSTANCE method, differently from a CLASS method,
needs to be passed the instance as the first argument, either
implicitly (by CALLING it on the instance) or explicitly
by passing it when calling the method on the class, as in:

Example.instmeth(inst)


Alex

"Grant Edwards" <> wrote in message
news:3f58b1f6$0$155$.. .
> In article <>, John Roth wrote:
> >
> > "Grant Edwards" <> wrote in message
> > news:3f58a2bd$0$156$.. .
> >> In article <>, John Roth wrote:
> >>
> >> > Technically, it would be possible to make "self" a reserved
> >> > word, and not have to put it in the method declaration.
> >> > However, there are a lot of people who use something other than
> >> > the word "self," so that would break existing code.
> >>
> >> It would also make the language more complex and irregular.
> >
> > How?
>
> 1) It would add a reserved word.

So? For most people, self *is* a reserved word anyway. A lot of
novices think it is. Making it official simplifies things, IMO.

> 2) It would mean that there's some sort of difference between
> a function and a method.

I don't understand your point. There is currently a difference
between a function and a method that could be eliminated by
making self a reserved word and removing it from the method
header. Or have you never tried to invoke a method from the
wrong context and gotten the "unbound method" error?

There's no reason why a function in the module space couldn't
use self to refer to the module. It would simplify things by
removing much of the need for the global keyword.

John Roth
>
> --
> Grant Edwards

"Mel Wilson" <> wrote in message
news:qpOW/ks/...
> In article <>,
> "John Roth" <> wrote:
> >"Grant Edwards" <> wrote in message
> >news:3f58b1f6$0$155$. ..
> >> In article <>, John Roth wrote:
> >> >
> >> > "Grant Edwards" <> wrote in message
> >> > news:3f58a2bd$0$156$.. .
> >> 2) It would mean that there's some sort of difference between
> >> a function and a method.
> >
> >I don't understand your point. There is currently a difference
> >between a function and a method that could be eliminated by
> >making self a reserved word and removing it from the method
> >header. Or have you never tried to invoke a method from the
> >wrong context and gotten the "unbound method" error?
>
> There's no difference in the sense that a method is
> simply a function whose first parameter refers to the class
> instance to be worked on. No magic words, no "undeclared"
> parameters. It means that in my demo code in limitcases.py
> (somewhere in the newsgroup lately) I can say
>
> limitcases.Lowest.__str__ = lambda x: "-Infinity"
>
> to give the Lowest class a new method sans ennuis.

But why do it that way? Neither Java nor Ruby require
giving the instance a name. Hence my comment that requiring
it is more complex than not requiring it.

John Roth
>
> Regards. Mel.