Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!gegeweb.org!de-l.enfer-du-nord.net!feeder2.enfer-du-nord.net!feeder.news-service.com!newsfeed.xs4all.nl!newsfeed5.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
MIME-Version: 1.0
Sender: chris@rebertia.com
In-Reply-To: <66a3f64c-d35e-40c7-be69-ddf708e37ba7@glegroupsg2000goo.googlegroups.com>
References: <66a3f64c-d35e-40c7-be69-ddf708e37ba7@glegroupsg2000goo.googlegroups.com>
Date: Sun, 28 Aug 2011 18:52:03 -0700
Subject: Re: Why I need the parameter when the call doesn't use it?
From: Chris Rebert <clp2@rebertia.com>
Cc: python-list@python.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.527.1314582726.27778.python-list@python.org>
Lines: 62
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: x330-a1.tempe.blueboxinc.net comp.lang.python:12372

On Sun, Aug 28, 2011 at 5:26 PM, Niklas Rosencrantz <niklasro@gmail.com> wr=
ote:
> I modularize code for a webapp and I want to know what python makes that =
a need to define an argument called self? Here's some code where I'm modula=
rizing a recaptcha test to a function and the I must add the parameter "sel=
f" to the function is_submitter_human:
>
> ----
> class A(BaseHandler, blobstore_handlers.BlobstoreUploadHandler):
> =C2=A0 =C2=A0def is_submitter_human(self):
> =C2=A0 =C2=A0 =C2=A0 =C2=A0cResponse =3D captcha.submit( =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 self.request.get('r=
ecaptcha_challenge_field').encode('utf-8'), =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 self.request.get('recaptcha_response=
_field').encode('utf-8'),
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 CAP=
TCHA_PRV_KEY,
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 os.=
environ['REMOTE_ADDR'])
> =C2=A0 =C2=A0 =C2=A0 =C2=A0return cResponse.is_valid
>
> =C2=A0 =C2=A0def post(self, view):
> =C2=A0 =C2=A0 =C2=A0 =C2=A0logging.debug('starting recaptcha check')
> =C2=A0 =C2=A0 =C2=A0 =C2=A0isHuman =3D self.is_submitter_human()# here I =
don't pass a parameter
> =C2=A0 =C2=A0 =C2=A0 =C2=A0logging.debug('recaptcha check isHuman:' +str(=
isHuman))
> =C2=A0 =C2=A0 =C2=A0 =C2=A0if not isHuman:#failed captcha and can try aga=
in
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0#Reprint the form
>
> --
> It seems unlike other programming languages where the number of arguments=
 in the call are the same as the number of arguments in the function head a=
nd python requires me to add one parameter to the function head and I wonde=
r if you call tell me something about the background why?
>
> What's the story of using these parameters that are called "self"?

Some other languages name the analogous parameter "this" instead of
"self", and basically declare it implicitly for you. In both cases,
said variable is used to refer to the object that the current method
is being called on (e.g. if `w` is a list and I do w.append(v), the
list `w` is `self` in the context of the .append() method call). Since
Python's object-orientation is slightly impure, you are required to
declare `self` explicitly in the parameter list, unlike most other
languages. Technically, you are free to name the parameter something
else instead of "self"; naming it "self" is merely a convention.
However, no matter its name, the first parameter to a method will
always receive the current object as its argument value.

So, given: x =3D Foo()
Then: x.bar(y, z)
is approximately equivalent to:
Foo.bar(x, y, z) # perfectly legal working code

So the number of arguments actually /does/ match the number of
parameters; `x`/`self` is just passed implicitly via the semantics of
the dot (".") operator.

Cheers,
Chris