On Wed, Apr 1, 2020 at 9:45 AM Thomas Passin wrote:
> It's really a comprehension vs brevity thing, and a matter of personal
> style.
>
No. It's a pylint bug. Enable the two checks and look at the warnings.
Edward
--
You received this message because you are subscribed to the Google Groups
It's really a comprehension vs brevity thing, and a matter of personal
style. Removing the else gives shorter code, which is *usually* more
clear. But without the *else*, you have to *infer* its virtual presence,
and that interferes with comprehension. I'm not consistent about this,
myself.
On Wed, Apr 1, 2020 at 8:52 AM vitalije wrote:
> I doubt that. A few days ago I've run pylint and it reported some
> complains about non necessary else after break, or after return. My first
> reaction was just like yours, but then I looked more closely and those
> complains were correct.
>
>
I doubt that. A few days ago I've run pylint and it reported some complains
about non necessary else after break, or after return. My first reaction
was just like yours, but then I looked more closely and those complains
were correct.
while True:
... # some code here
if condition:
leo/test/pylint-leo-rc-ref.txt now disables the following two new tests:
no-elif-break
no-else-break
Imo, these are just plain wrong. Following the pylint advice would change
the meaning of the program. These look like serious pylint bugs.
Edward
--
You received this message because
