[issue29323] Wrong documentation (Library) for unicode and str comparison

Serhiy Storchaka added the comment: Python 2.7 is no longer supported. -- nosy: +serhiy.storchaka resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker

[issue29323] Wrong documentation (Library) for unicode and str comparison

R. David Murray added the comment: That's a good point, I think that is exactly the issue with that paragraph. -- ___ Python tracker ___

[issue29323] Wrong documentation (Library) for unicode and str comparison

Martin Panter added the comment: If you read the whole paragraph carefully, I don't think it is too misleading. "In particular, tuples and lists . . ." suggests the author was just trying to say that a tuple never compares equal to a list. Maybe we just need to make that more obvious?

[issue29323] Wrong documentation (Library) for unicode and str comparison

R. David Murray added the comment: As per your other issue, though, the real issue is that the two objects must be *comparable*, not that they be of the same type, and the language should probably be updated to reflect that. -- ___ Python tracker

[issue29323] Wrong documentation (Library) for unicode and str comparison

R. David Murray added the comment: Unicode and string *are* of the same type: basestring. This is a specific example of the liskov substitution principle, so I don't think it should be called out explicitly in this section. -- nosy: +r.david.murray

[issue29323] Wrong documentation (Library) for unicode and str comparison

New submission from RK-5wWm9h: PROBLEM (IN BRIEF): In the currently published 2.7.13 The Python Standard Library (Library Reference manual) section 5.6 "Sequence Types" (https://docs.python.org/2/library/stdtypes.html#sequence-types-str-unicode-list-tuple-bytearray-buffer-xrange): "to