Steven D'Aprano wrote:
As for why None, True and False are treated differently than built-ins,
if I remember the reason why, it is because they are considered
fundamental to the inner workings of Python, unlike mere builtins like
len, map, etc. and therefore should be protected.
It's probably
On Fri, 23 Aug 2013 16:38:43 -0700, jeangawron wrote:
> Python allows you set the value of True
>
True = 1.3
Only in older versions of Python. This is for historical reasons: True
and False were added as built-ins relatively late in Python's history
(2.2, I think) and so there is still ol
On 8/23/2013 7:38 PM, jeangaw...@gmail.com wrote:
Python allows you set the value of True
Unqualified 'Python', used in the present tense, refers to the latest
release or repository version.
>>> True = 1.3
SyntaxError: assignment to keyword
True = 1.3
Now this is consistent with the deci
On 08/23/2013 04:38 PM, jeangaw...@gmail.com wrote:
Python allows you set the value of True
True = 1.3
Now this is consistent with the decision to let you set the
value of various builtin names. But why is this case different:
None = 1.3
File "", line 1
SyntaxError: cannot assign to Non
