Re: [PyChecker-list] Using is None, may not always work

[Neal N. <nno...@gm...>]

On Wed, 26 Jan 2005 15:41:48 -0800, Grant Monroe <gr...@tn...> wrote:
> Here is a patch for the warnings that started appearing in Python 2.4
> about "x is None" not always working. This is happening because None is
> a constant in 2.4.
> 
> When PyChecker sees the constant it supposes you are doing something like
> 
>    if x is "some string": pass
> 
> which always had the LOAD_CONST op-code and is indeed dangerous.

Thanks Grant.  I think this is fixed in CVS, but I'll check.

Neal