Striving for PEP-8 compliance

[Steve Howell]

On Apr 14, 1:10 pm, Hans Mulder <han... at xs4all.nl> wrote:
> Grant Edwards wrote:
> > On 2010-04-09, Lawrence D'Oliveiro <l... at geek-central.gen.new_zealand> wrote:
> >> In message <4bbf6eb8$0$1670$742ec... at news.sonic.net>, John Nagle wrote:
>
> >>> Lawrence D'Oliveiro wrote:
>
> >>>> In message <mailman.1610.1270655932.23598.python-l... at python.org>,
> >>>> Gabriel Genellina wrote:
>
> >>>>> If you only reindent the code (without adding/removing lines) then you
> >>>>> can compare the compiled .pyc files (excluding the first 8 bytes that
> >>>>> contain a magic number and the source file timestamp). Remember that
> >>>>> code objects contain line number information.
> >>>> Anybody who ever creates another indentation-controlled language should
> >>>> be beaten to death with a Guido van Rossum voodoo doll.
> >>>     No ...
> >> Yes, because otherwise you wouldn?t have stupid problems like the one
> >> which is preoccupying this thread: how to make sure indentation is
> >> consistent without introducing logic errors into the code.
>
> > Anybody who invents another brace-delimited language should be beaten.
> > You always end up with a big problem trying to make sure the braces
> > are consistent with the program logic.
>
> Anybody who invents another programming language should be beaten.
> You always end up with a big problem trying to make sure the program
> logic is consistent with the customers's needs :-(

The world still needs new programming languages.  People in 2050 will
look back at 2010 and laugh at the fact that Py3K was considered
halfway innovative.  Indentation based syntax will be so common that
no one will even remember squigglies, end tags, or asymmetric memory
allocation schemes.