mal wrote:
>> How about adding a new pure bool type to the language
> *without* changing any of the old Py_False/Py_True
> code (at first) ?!
>=20
> Then leave the code in for one release to see how
> people feel about it in real life and enable a warning
> for incorrect usage of comparison arithmetic in a second=20
> release. The third release would then enable the new
> logic per default.
from __future__ import boolean ?
(maybe it's time to introduce a __yagni__ module for people
who prefer Harlin over van der Rohe? ;-)
</F>
