Disable (subset of) comparison dunder methods inherited from tuple

[bskinn]

In the course of trying to figure out a way to report the method inheritance cascade, I noticed that, e.g, StdioManager has the comparison methods inherited from tuple:

__le__               :: <slot wrapper '__le__' of 'tuple' objects>
__lt__               :: <slot wrapper '__lt__' of 'tuple' objects>

Comparing tuples of stream objects, with the possible exception of == and !=, makes no sense.

Probably the best solution is an intervening class in the hierarchy, say NoCompTuple, which overrides __le__ et al. with a simple return NotImplemented?

[bskinn]

Although, I guess it's probably fine to just let the natural TypeError propagate up, from when tuple tries its element-wise comparisons.

(In)equality seems to work ok on the tuple base.

Probably can just close this w/o action, @jayvdb?