think most programmers know that 0 is false and 1 is true, and I weant to get rid of drBoolean.py, as well as make sure we use ints (wxPython 2.5.x uses booleans, which leads to a compat issue (fixed) with prefs.)
What thoughts?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I agree with limodou that "True" and "False" are much more readable, and to be honest, I've become so used to
using them (originally via constant declarations a la drBoolean) that I'd miss them.
That said, I can always to a quick "find" when I've finished coding to make sure I've not used them, so go ahead if you feel it would be of benefit.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am thinking of killing booleans in drpython.
think most programmers know that 0 is false and 1 is true, and I weant to get rid of drBoolean.py, as well as make sure we use ints (wxPython 2.5.x uses booleans, which leads to a compat issue (fixed) with prefs.)
What thoughts?
In 2.3.3, Python has build-in boolean type True and False. Yes, we don't need drBoolean.py. But using True and False may be more clearly in some case.
So then you support using True and False, and telling people they need to use the latest Python (2.2 or later)?
I agree with limodou that "True" and "False" are much more readable, and to be honest, I've become so used to
using them (originally via constant declarations a la drBoolean) that I'd miss them.
That said, I can always to a quick "find" when I've finished coding to make sure I've not used them, so go ahead if you feel it would be of benefit.