Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #12654 > unrolled thread
| Started by | Dennis Lee Bieber <wlfraed@ix.netcom.com> |
|---|---|
| First post | 2011-09-02 10:15 -0700 |
| Last post | 2011-09-02 10:15 -0700 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: allow line break at operators Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2011-09-02 10:15 -0700
| From | Dennis Lee Bieber <wlfraed@ix.netcom.com> |
|---|---|
| Date | 2011-09-02 10:15 -0700 |
| Subject | Re: allow line break at operators |
| Message-ID | <mailman.712.1314984009.27778.python-list@python.org> |
On Fri, 2 Sep 2011 14:14:12 +0800, Gabriel AHTUNE
<gahtune@gmail.com> declaimed the
following in gmane.comp.python.general:
> So can be done with this syntax:
>
> > x = firstpart * secondpart + #line breaks here
> > anotherpart + #continue
> > stillanother #continue on.
>
> after a "+" operator the line is clearly not finished yet.
>
Which would get a NO vote from me, as I routinely line up operators
on the left
x = firstpart * secondpart
+ anotherpart
+ stillanother
especially when grouping by operator precedence
x = (a * b #parens to make
+ x / y #valid python
+ m**n)
Besides, that trailing operator can visually become lost in the
clutter of comments on the same line... Compare that sample to
x = (a * b + #parens to make valid python
x / y + #valid python
m**n)
--
Wulfraed Dennis Lee Bieber AF6VN
wlfraed@ix.netcom.com HTTP://wlfraed.home.netcom.com/
Back to top | Article view | comp.lang.python
csiph-web