0 == False but [] != False? - comp.lang.python

Message from discussion 0 == False but [] != False?

Steven D'Aprano

View profile

More options May 30 2007, 8:59 am

Newsgroups: comp.lang.python

From: Steven D'Aprano <st...@REMOVE.THIS.cybersource.com.au>

Date: Wed, 30 May 2007 08:59:37 +1000

Local: Wed, May 30 2007 8:59 am

Subject: Re: 0 == False but [] != False?

  Reply to author
  |
  Forward
  | Print
  | View thread
  | Show original
  | Report this message
  | Find messages by this author
  

On Tue, 29 May 2007 11:36:07 -0700, Erik Max Francis wrote:
> Donn Cave wrote:

>> Not that it is of no historical interest to review all these
>> reasonable arguments, but allow me to restore the context quote
>> from my follow-up:

> If the counterpoints are of no historical interest, then the original
> point must be of no historical interest either, since it was not widely
> granted as true.

I hope you don't get just as confused by expressions like:

if not x != 5

*wink*

In English, a double negative is usually a positive. So "Not that it is of
no historical interest" means "It is of historical interest".

I wonder, if somebody with more time on their hands than me were to go
through the threads on comp.lang.python before and after the introduction
of bools, could we determine whether there were more problems caused by
the introduction of True and False than by the lack of them? Although I
like using bools, in my heart of hearts I suspect that Laura was right.

--
Steven.

Reply to author Forward