'Using is not None, may not always work'

[Heiko Wundram]

Am Freitag, 6. August 2004 15:15 schrieb Doug Fort:
> Since I installed 2.4a2 I've been getting a warning from pychecker: Using
> is not None, may not always work'. I thought 'is not None' was the right
> thing to do. I've had problems with 'if not x:', because some objects
> return False in this context.

That's probably what pychecker warns you about: that you might get an object 
in the respective context which evaluates to boolean false, but is not 
None... Although I'd find this strange...

Heiko.