R
Rodney Maxwell
In Python 2.4.1:
True
True
Rodney Maxwell said:In Python 2.4.1:
True
A legacy/backwards compatibility issue: None has been there 'forever',
so that no sensible code ever had any business assigning to it; but
'False' and 'True' were introduced just a few years ago, and it was
important to not break sensible existing code doing something like
True = 1
False = 0
at the very start. In Python 3.0, when backwards compatibilities can be
introduced, True and False will become keywords (as will None); see
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.