This seems like it’s specific to the packaging library, so it’s probably better raised as an issue with them. I’m not sure how I’d even go about comparing two general requirements (such as foo>1.0 and foo>=2.0, for example - they aren’t literally equal, but they may match the same set of releases if there’s no 1.x versions other than 1.0). The semantics of comparing Requirement objects is more a matter of what the library chooses than a standards matter IMO.
It was me, yes - thanks for confirming it. It was more of “is this behavior what’s being discussed in this issue”, which was not clear to me initially. We can continue the conversation there.