Ethan Furman added the comment: Mike, my apologies. In the future I'll make sure and read the docs before I go through with changes.
In the docs (https://www.python.org/dev/peps/pep-0435/#id35): The reason for defaulting to 1 as the starting number and not 0 is that 0 is False in a boolean sense, but enum members all evaluate to True. >From a newer discussion on Python Ideas and Python Dev: Barry Warsaw: I think in general enums are primarily a symbolic value and don't have truthiness. It's also so easy to override when you define the enum that it's not worth changing the current behavior. Guido van Rossum: Honestly I think it's too late to change. The proposal to change plain Enums to False when their value is zero (or falsey) would be a huge backward incompatibility. I don't think there's a reasonable path forward, and also don't think there's a big reason to regret the current semantics. Thank you, Gregory, for catching that. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue24840> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
