bool constructor is inconsistent?

[Neal Becker]

IN [3]: bool('False')
Out[3]: True

In [4]: int('32')
Out[4]: 32

 

[Stefan Schwarzer]

Hi Neal,

IN [3]: bool('False')
Out[3]: True

If you consider strings, only an empty string has a false
value. So the string 'False' which is non-empty, results in
a true boolean value.

For example, you can use

if my_string:
...

to execute some code if the string is not empty.

Stefan

 

[David Robinow]

Hi Neal,

IN [3]: bool('False')
Out[3]: True

If you consider strings, only an empty string has a false
value. So the string 'False' which is non-empty, results in
a true boolean value.
...

I've always felt that if a humorous post needs a smiley, that it's not funny.
However, there is the risk of being misunderstood.

 

[Steven D'Aprano]

IN [3]: bool('False')
Out[3]: True

In [4]: int('32')
Out[4]: 32

Where is the inconsistency? bool('False') returns the same result as for
any other non-empty string:
True



Treating the string "False" as identical to the named global False would
be inconsistent.