You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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 fromtuple
: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 simplereturn NotImplemented
?The text was updated successfully, but these errors were encountered: