fix(pipstar): handle a corner case for compatible version evaluation by aignas · Pull Request #3583

fix(pipstar): handle a corner case for compatible version evaluation by aignas · Pull Request #3583 · bazel-contrib/rules_python

It seems that there was one corner case that was left unhandled.
In theory we should also handle `3 ~= 3.0.0`, but the fix for that may
be a little more involved and I want to leave it for later.

Fixes bazel-contrib#3580

aignas deleted the aignas.fix.version-specifiers branch

February 11, 2026 03:48

aignas added a commit that referenced this pull request

Feb 11, 2026

…3583)

It seems that there was one corner case that was left unhandled.
In theory we should also handle `3 ~= 3.0.0`, but the fix for that may
be a little more involved and I want to leave it for later. However,
that case is unlikely to occur in reality because `LHS` for our cases
will most likely have 2 components.

Whilst at it prepare for the patch release (#3584).

Fixes #3580

(cherry picked from commit a32c744)

aignas added a commit to aignas/rules_python that referenced this pull request

Feb 23, 2026

…azel-contrib#3583)

It seems that there was one corner case that was left unhandled.
In theory we should also handle `3 ~= 3.0.0`, but the fix for that may
be a little more involved and I want to leave it for later. However,
that case is unlikely to occur in reality because `LHS` for our cases
will most likely have 2 components.

Whilst at it prepare for the patch release (bazel-contrib#3584). 

Fixes bazel-contrib#3580