On Mon, Oct 29, 2012 at 3:30 PM, Evan Driscoll wrote:
> On 10/28/2012 7:18 PM, Chris Angelico wrote:
>> Which means that strings will ALWAYS be compared as strings, and
>> numbers will ALWAYS be compared as numbers, and ne'er the twain shall
>> conflict. I can trust Python to compare MD5 hashes re
On 10/28/2012 7:18 PM, Chris Rebert wrote:
> This is fixed in Python 3, where such nonsensical comparisons will
> instead raise TypeError.
It's worth pointing out that at least one kind of inequality comparison
which some people (e.g. me) would consider nonsensical is still allowed
in Python 3, wh
On Mon, Oct 29, 2012 at 10:51 AM, Mark L. Hotz wrote:
> At the IDLE prompt, when I enter “b” > 99, it responds True. In fact, it
> doesn’t matter which number is entered here, “b” is always greater (e.g. “b”
>> 1 == True; “b” > 10 == True, or “b” < 99 = False).
To Python, different object typ
On Sun, Oct 28, 2012 at 4:51 PM, Mark L. Hotz wrote:
> I have what I think should be a relatively simple question for someone who
> is knowledgeable about Python.
>
> At the IDLE prompt, when I enter “b” > 99, it responds True. In fact, it
> doesn’t matter which number is entered here, “b” is alwa
On 28/10/2012 23:51, Mark L. Hotz wrote:
I have what I think should be a relatively simple question for someone who
is knowledgeable about Python.
Sorry you've come to the wrong place :)
At the IDLE prompt, when I enter "b" > 99, it responds True. In fact, it
doesn't matter which number is e
