On Fri, Nov 04, 2011 at 11:10:58AM -0400, Steven Lehar wrote:
> 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
On 11/4/2011 11:10 AM, Steven Lehar wrote:
Is this the right place to propose language extensions?
Yes, especially for beginners not familiar with previous discussions.
My Python code keeps expanding rightwards, it is difficult to keep it
contained within reasonable limits. But the standard l
On Sat, Nov 5, 2011 at 2:53 AM, Steven Lehar wrote:
>
> >
> 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,
> so
>
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
On Sat, Nov 5, 2011 at 2:10 AM, Steven Lehar wrote:
> But the standard line continuation \
> is positively anti-Pythonic because an *invisible* white space between \ and
> [CR] will render it useless.
How's it anti-Pythonic for invisible whitespace differences to be significant?
ChrisA
*grinni
Steven Lehar wrote:
> 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.
You should attack this by breaking large expressions into smaller ones and
factoring out some of your co
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
