The way I see it, the two statements can co-exist. There’s no need for new types to support a tuple API for backward compatibility - a usage like sys.version_info > (3, 15) is evidently for more reasons than simply backward compatibility.
The way I see it, the two statements can co-exist. There’s no need for new types to support a tuple API for backward compatibility - a usage like sys.version_info > (3, 15) is evidently for more reasons than simply backward compatibility.