Message382463
I'm not _sure_ this is a bug, but I thought the behaviour was a bit odd. If you run max with a str and an int in different orders, you get this behaviour:
>>> max(123, 'hello')
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
TypeError: '>' not supported between instances of 'str' and 'int'
>>> max(123, 'hello')
>>> max('hello', 123)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
TypeError: '>' not supported between instances of 'int' and 'str'
Note that order of the error message: 'int' and 'str' is the inverse of the order the str and int really are.
Did a search for max and didn't find this. |
|
Date |
User |
Action |
Args |
2020-12-04 00:57:36 | nkobald | set | recipients:
+ nkobald |
2020-12-04 00:57:36 | nkobald | set | messageid: <1607043456.77.0.380335998391.issue42563@roundup.psfhosted.org> |
2020-12-04 00:57:36 | nkobald | link | issue42563 messages |
2020-12-04 00:57:36 | nkobald | create | |
|