Victor Stinner writes:
> Hum.
>
> if (width == 0
> and height == 0
> and color == 'red'
> and emphasis == 'strong'
> or highlight > 100):
> raise ValueError("sorry, you lose")
>
> Please remove one space to vertically a
Hi,
On 04/15/2016 07:43 PM, Guido van Rossum wrote:
> The update is already serving its real purpose: showing that style is
> debatable and cannot always easily be reduced to fixed rules.
>
As you said, there will be always some kind personal preferences or
style taste and one can see on the deb
On Fri, Apr 15, 2016, at 23:46, Peter Ludemann via Python-Dev wrote:
> If Python ever adopts the BCPL rule for implicit line continuation if
> the last thing on a line is an operator (or if there's an open
> parentheses), then the break-after-an-operator rule would be more
> persuasive. ;)
>
> [IIR
If Python ever adopts the BCPL rule for implicit line continuation if the
last thing on a line is an operator (or if there's an open parentheses),
then the break-after-an-operator rule would be more persuasive.
;)
[IIRC, the BCPL rule was that there was an implicit continuation if the
grammar woul
Cross posting the comment I’d left on the issue [1].
> My preference is to actually break that logic up and avoid the wrapping in
> the first place, as in [2]. Which in this particular class has the side
> benefit of that value being used again in the same function anyways.
> I'm starting to re
On Apr 15, 2016, at 09:53 AM, Guido van Rossum wrote:
>After a fruitful discussion on python-ideas I've decided that it's fine to
>break lines *before* a binary operator.
Thanks Guido, your changes look great.
-Barry
___
Python-Dev mailing list
Python-
On 2016-04-15 18:03, Victor Stinner wrote:
> Hum.
>
> if (width == 0
> and height == 0
> and color == 'red'
> and emphasis == 'strong'
> or highlight > 100):
> raise ValueError("sorry, you lose")
>
> Please remove one space
The update is already serving its real purpose: showing that style is
debatable and cannot always easily be reduced to fixed rules.
On Fri, Apr 15, 2016 at 10:24 AM, Serhiy Storchaka
wrote:
> On 15.04.16 20:03, Victor Stinner wrote:
>
>> Hum.
>>
>> if (width == 0
>> and hei
On 15.04.16 20:03, Victor Stinner wrote:
Hum.
if (width == 0
and height == 0
and color == 'red'
and emphasis == 'strong'
or highlight > 100):
raise ValueError("sorry, you lose")
Please remove one space to vertically align
On Fri, Apr 15, 2016 at 10:03 AM, Victor Stinner
wrote:
> Hum.
>
> if (width == 0
> and height == 0
> and color == 'red'
> and emphasis == 'strong'
> or highlight > 100):
> raise ValueError("sorry, you lose")
>
> Please remove on
On 15 April 2016 at 18:03, Victor Stinner wrote:
> Hum.
>
> if (width == 0
> and height == 0
> and color == 'red'
> and emphasis == 'strong'
> or highlight > 100):
> raise ValueError("sorry, you lose")
>
> Please remove one space
[Guido]
> After a fruitful discussion on python-ideas I've decided that it's fine to
> break lines *before* a binary operator. It looks better and Knuth recommends
> it.
> ...
> Therefore it is permissible to break before or
> after a binary operator, as long as the convention is consistent
> local
Hum.
if (width == 0
and height == 0
and color == 'red'
and emphasis == 'strong'
or highlight > 100):
raise ValueError("sorry, you lose")
Please remove one space to vertically align "and" operators with the
opening parenthesis:
13 matches
Mail list logo
