On Fri, May 29, 2015 at 1:20 PM, <random...@fastmail.us> wrote: > The possibility of spelling these with the comparison operators, as some > have suggested, is a consequence of Python's implementation where True > == 1 and False == 0. In other languages bool may not be relatable (or at > least not orderable), or False may be == -1.
True. That said, though, using 0 for False and 1 for True is easily the most common convention in use today, and the next most likely case is that comparing booleans would give a simple and immediate error. So it's most likely to be safe to do. Cross-language compatibility is a tricky thing anyway; there are all sorts of odd edge cases, even with otherwise-similar languages (Pike and Python, for instance, have slightly different handling of slice ranges), so anything that's done in Python is meant to be interpreted with Python semantics. ChrisA -- https://mail.python.org/mailman/listinfo/python-list
