On 15 June 2013 19:28, Dave Angel <da...@davea.name> wrote: > If you want to compare a non-boolean to False or True, expect it'll always > be false. They are different types. (except for the int historical > nonsense I mentioned earlier).
Ah, that clarifies it - type differences - something I can look out for - and throwing in the 1, 0 baloney, which I was hoping to get away from when I decided to do Python instead of Javascript. I may be lazy but I really don't need to substitute 0 for False. -- Jim After indictment the bacon smuggler was put on the no-fry list _______________________________________________ Tutor maillist - Tutor@python.org To unsubscribe or change subscription options: http://mail.python.org/mailman/listinfo/tutor
