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>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4