Fredrik Lundh wrote:
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) ?!
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 release. The third release would then enable the new logic per default.
from __future__ import boolean ?
Hmm, would be nice, but has a flaw: the change wouldn't be limited to one module: it would affect the current instance of the interpreter. Still, a switch like this would be nice to have... probably too late though: Guido has already decided that its better to rush this than come up with a less controversial design. -- Marc-Andre Lemburg CEO eGenix.com Software GmbH ______________________________________________________________________ Company & Consulting: http://www.egenix.com/ Python Software: http://www.egenix.com/files/python/