Re: Python != None

2024-02-25 Thread Dima Pasechnik
On Sun, Feb 25, 2024 at 11:29:51AM -0800, Collin Funk wrote: > On 2/25/24 3:57 AM, Bruno Haible wrote: > > The style warnings about "!= None" in pycodestyle and/or pylint are > > relativized by this warning in Python itself: > > > > >>> '' != None > > True > > >>> '' is not None > > :1: Sy

Re: Python != None

2024-02-25 Thread Collin Funk
On 2/25/24 11:29 AM, Collin Funk wrote: > I would hope that it just > involves a simple configuration file that takes the options we have at > the top of gnulib-tool.py. Adding the two attached files to the root directory of gnulib should adjust the warnings to the agreed upon coding style (as far

Re: Python != None

2024-02-25 Thread Collin Funk
Hi Bruno, On 2/25/24 3:57 AM, Bruno Haible wrote: > The style warnings about "!= None" in pycodestyle and/or pylint are > relativized by this warning in Python itself: > > >>> '' != None > True > >>> '' is not None > :1: SyntaxWarning: "is not" with a literal. Did you mean "!="? > True

Re: Python != None

2024-02-25 Thread Bruno Haible
Collin Funk wrote: > One thing that annoys me personally > is comparing to none using "!=" instead of "is not". This is > recommended against in PEP 8, "Comparisons to singletons like None > should always be done with is or is not, never the equality > operators." [1]. Dima Pasechnik wrote: > The