Bug: Requirement leaks InvalidSpecifier instead of raising InvalidRequirement for malformed specifier lists
Bug: Requirement leaks InvalidSpecifier instead of raising InvalidRequirement for malformed specifier lists: a task in repo2rlenv-swe-next (Harbor dataset). When parsing a requirement string like demo===x,y , the requirement parser accepts the name and specifier portion, but the subsequent…
The task
When parsing a requirement string like `demo===x,y`, the requirement parser accepts the name and specifier portion, but the subsequent `SpecifierSet` construction rejects the bare `y` token. Instead of wrapping this failure as `InvalidRequirement`, the raw `InvalidSpecifier` exception propagates out of `Requirement()`.
Part of FineEnvs/repo2rlenv-swe-next.