Many thanks to all who responded to my "Python Classes: Simplify?" thread.
There seem to be several good reasons for this particular syntactical
choice, I am all the wiser for your kind explanations. My faith in the
simplicity and elegance of this beautiful language is reinforced.
Thanks all!
--
Reply to Steve Howell
>>>
Do you think we'll always have a huge number of incompatible
programming languages? I agree with you that it's a fact of life in
2012, but will it be a fact of life in 2062?
<<<
We can only HOPE so!
When I first learned unix / sh / csh / tcsh / bash ...etc... it irked
It seems to me that the Python class system is needlessly confusing. Am I
missing something?
For example in the class Complex given in the documentation
*class Complex:*
*def __init__(self, realpart, imagpart):*
*self.r = realpart*
*self.i = imagpart*
*
*
*x = Complex(3.0, -4.
>
How's it anti-Pythonic for invisible whitespace differences to be
significant?
A central idea of Python was to replace {curly;braces{and;parentheses;}},
which are easily overlooked by the programmer, and use WHITESPACE instead,
something that is clearly visible to the programmer, as the defining
Is this the right place to propose language extensions?
My Python code keeps expanding rightwards, it is difficult to keep it
contained within reasonable limits. But the standard line continuation \
is positively anti-Pythonic because an *invisible* white space between \
and [CR] will render it us
