numeric range equality doesn't match built-in range semantics for single-element ranges

numeric range equality doesn't match built-in range semantics for single-element ranges: a task in repo2rlenv-swe-next (Harbor dataset). Since Python 3.3, range objects are compared based on the sequence of values they define, not their internal parameters. For example: