allow line break at operators

Chris Angelico rosuav at gmail.com
Fri Aug 12 01:58:30 CEST 2011


On Thu, Aug 11, 2011 at 10:19 PM, Seebs <usenet-nospam at seebs.net> wrote:
> I am pretty sure Python is a pretty nice language.  However, the indentation
> thing has screwed me a few times.  Furthermore, I know people who like Python
> a great deal and acknowledge, without much difficulty, that the indentation
> thing has caused problems or incompatibilities for them.
>

Indentation-is-syntax is a feature of Python, and one that's not
likely to change. Some programmers do not like indentation to be
syntax, and a lot of them are not likely to change their views.
There's a solution to this dilemma; it's called "using another
language".

Python is just one of many excellent languages in the world today.
Even if you exclude non-free languages and non-free
compilers/interpreters, you still have a wealth of options. Check
Wikipedia, find one in a category that interests you, download a
development environment, and give it a shot!

It would surprise me *greatly* if the regular posters on this list
were not all familiar with several languages other than Python,
including at least one bracey language. The arguments do not come from
ignorance but from knowledge. Incidentally, I will happily argue the
benefits of Python's significant whitespace, even though I disagree
with it; there are quite a few. (Is the fact that it discourages
massive one-liners considered to be a benefit?)

Of course, sometimes choosing another language is a luxury you can't
afford. But in those situations, usually you're slotting into someone
else's code Manual of Style too, so you might be required to write C
code with three-space indents and a blank line before every open
brace, for all we know. Doesn't matter that you're in a
whitespace-insignificant language; you are in a whitespace-significant
*environment*, and that's what matters.

Chris Angelico



More information about the Python-list mailing list