None is handy and I like it, but it's arbitrary enough in some cases that it takes time to get used to its quirks (e.g., why is a value that's "not really there" considered to be false? why not? sometimes that's what you want; sometimes you'd rather get an exception; None picks an arbitrary answer and sticks to it), so I don't want see more things like it proliferate (one is enough -- but not too many <wink>).
None inherits most of its semantics from C's NULL -- that's where None being false comes from.
--Guido van Rossum (home page: http://www.python.org/%7Eguido/)