In fact, it's striking me that there may well be classes that are
defining the comparison magic methods not because they want the objects
to "work" with the comparison operators, but because that want them to
work with sort and min, and max, and...
Granted, calling min() and max() on collections of these objects would not make conceptual sense either. Still, __sort_key__ would have been cleaner than __lt__.