Bug: LowerBound(None, True) and UpperBound(None, True) don't normalize inclusive to False
Bug: LowerBound(None, True) and UpperBound(None, True) don't normalize inclusive to False: a task in repo2rlenv-swe-next (Harbor dataset). When constructing an unbounded lower or upper bound (i.e., with version=None , representing -∞ or +∞), passing inclusive=True is accepted and stored as-is…
The task
When constructing an unbounded lower or upper bound (i.e., with `version=None`, representing -∞ or +∞), passing `inclusive=True` is accepted and stored as-is. This causes two different spellings of the same conceptual bound to compare as unequal and sort differently from each other.
Part of FineEnvs/repo2rlenv-swe-next.