Groups > comp.lang.python > #32056

Re: classes

References	(1 earlier) <5087E540.8060504@davea.name> <CAFqGZRFxfe=_N+1mhSD7ObedHgy6j9vKUhMgbU0smfOEC-wEyg@mail.gmail.com> <CANaSqUeHEvoPvuKzMOsYD8z1s6sXDV1XJQOZKvBh+cbd=n7pGQ@mail.gmail.com> <CAPTjJmoEwnrsPsHEO7wRqKhyNd_P3qDpXu3bRfOPfZF0FSY69g@mail.gmail.com> <CANaSqUdmjSNUvX-Urf0U2avVgxpxs47TNTCzEOpYZ4+QZhYzSA@mail.gmail.com>
Date	2012-10-25 03:29 +1100
Subject	Re: classes
From	Chris Angelico <rosuav@gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.2785.1351096146.27098.python-list@python.org> (permalink)

Show all headers | View raw

On Thu, Oct 25, 2012 at 3:10 AM, Zero Piraeus <schesis@gmail.com> wrote:
> On 24 October 2012 11:18, Chris Angelico <rosuav@gmail.com> wrote:
>> On Thu, Oct 25, 2012 at 2:14 AM, Zero Piraeus <schesis@gmail.com> wrote:
>>> [... on return values and side effects ...]
>>
>> Side point: It's not that it's *bad* code or even bad style;
>
> It's a matter of taste, sure, but especially for a beginner, it's easy
> to find yourself using a method for its return value and forgetting
> that it actually does something to the object as well ... and then
> getting bitten later.
>
>> it just isn't the way Python generally does things.
>
> When in Rome ... :-)

Of course, and I'm not disagreeing with the original point made. It's
worth writing Pythonic code when writing Python code. It's just not
the only way to write.

ChrisA

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

Thread

Re: classes Chris Angelico <rosuav@gmail.com> - 2012-10-25 03:29 +1100

csiph-web