Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!gegeweb.org!de-l.enfer-du-nord.net!feeder1.enfer-du-nord.net!feeder.erje.net!newsfeed.xs4all.nl!newsfeed6.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Using the Python Interpreter as a Reference
Date: Fri, 2 Dec 2011 15:29:22 -0500
In-Reply-To: <4ed81f16$0$29988$c3e8da3$5496439d@news.astraweb.com>
Thread-Topic: Using the Python Interpreter as a Reference
Thread-Index: Acywi9JjifHP2imLQ0GTOkSBBb8rqQApRTbg
References: <79379487-0081-4067-92ed-c6717652e1ff@y7g2000vbe.googlegroups.com><ebcb6b27-a1bd-402d-9571-7a86fd460a01@h42g2000yqd.googlegroups.com><4eb0af60-26b3-45d5-8aff-566505003d6a@m10g2000vbc.googlegroups.com><4ed2cddc$0$29988$c3e8da3$5496439d@news.astraweb.com><ca5fc7af-acf9-4422-bb2e-b25a7a2384ca@cc2g2000vbb.googlegroups.com><mailman.3113.1322531392.27778.python-list@python.org><4ed491fe$0$14018$c3e8da3$76491128@news.astraweb.com><dfd0539d-9abe-44a0-bbd0-5678d85ddc3f@i8g2000vbh.googlegroups.com> <4ed81f16$0$29988$c3e8da3$5496439d@news.astraweb.com>
From: "Sells, Fred" <fred.sells@adventistcare.org>
To: "Steven D'Aprano" <steve+comp.lang.python@pearwood.info>, <python-list@python.org>
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.3237.1322857841.27778.python-list@python.org>
Lines: 70
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: x330-a1.tempe.blueboxinc.net comp.lang.python:16569

Steven, that's probably the most elegant explanation of the "pythonic"
way I've ever seen.  I'm saving it for the next time upper management
want to use Java again.

-----Original Message-----
From: python-list-bounces+frsells=3Dadventistcare.org@python.org
[mailto:python-list-bounces+frsells=3Dadventistcare.org@python.org] On
Behalf Of Steven D'Aprano
Sent: Thursday, December 01, 2011 7:43 PM
To: python-list@python.org
Subject: Re: Using the Python Interpreter as a Reference

On Thu, 01 Dec 2011 10:03:53 -0800, DevPlayer wrote:

[...]
> Well, that may be a little hyperbolic. But with 2 spaces you can
> encourage coders to get very deep, indentially, and still fit 80
chars.

Why would you want to encourage coders to write deeply indented code?

In my opinion, if your code is indented four or more levels, you should=20
start to think about refactorising your code; if you reach six levels,=20
your code is probably a mess.

class K:
    def spam():
        if x:
            for a in b:
                # This is about as deep as comfortable
                while y:
                    # Code is starting to smell
                    try:
                        # Code smell is now beginning to reek
                        with z as c:
                            # And now more of a stench
                            try:
                                # A burning, painful stench
                                if d:
                                    # Help! I can't breathe!!!
                                    for e in f:
                                        # WTF are you thinking?
                                        try:
                                            # DIE YOU M***********ER!!!
                                            while g:
                                                # gibbers quietly
                                                ...


The beauty of languages like Python where indentation is significant is=20
that you can't hide from the ugliness of this code.=20

class K: {
  # Code looks okay to a casual glance.
  def spam():{
   if x: { for a in b:{
     while y:{ try:{ with z as c:{
       try:{ if d:{ for e in f:{ try:{
         while g:{ ... }}}}
       }}}}
     }}}}

Deeply indented code *is* painful, it should *look* painful.


--=20
Steven
--=20
http://mail.python.org/mailman/listinfo/python-list