String to boolean conversion about undictify

[Dobiasd]

Usually I'd say the default behaviour of Python might be the least surprising to a user of a library. But in that particular case it would mean that converting 'False' to True is the "sane" thing to do. But this does not sound very sane to me. 🙂

So I guess it might make sense to handle this in undictify. What strings should we convert to True and False? Maybe like so?

• True <- ['1', 'yes', 'true', 'on']
• False <- ['0', 'no', 'false', 'off']
• exception for everything else?

(With the string being converted to lowercase first?)

[Dobiasd]

It just makes so much sense, so I quickly implemented it. :)

[Dobiasd]

Thanks again a lot for this very helpful report. Stuff like this really improves the library. :)

[LukeMathWalker]

Wow, I wasn't even able to answer - thanks so much for the quick response!
I don't about on/off or yes/no, but 0/1 and false/true for sure make sense :)

[Dobiasd]

If a component in the the standard library does it that way, I guess it's fine. :)