Repository navigation
Fix version equality when hashes collide - #50
sylvesterkaczmarek wants to merge 1 commit into
Conversation
d05a4ed to
4cddf5f
Compare
|
|
Revalidated #50 with the full project checks: 269 unit tests pass under The source tree is unchanged; I refreshed the commit as SSH-verified 4cddf5f. The PR is 0 behind and mergeable, and the existing Sonar quality gate is passing. The three fork-triggered Actions workflows are currently |
|
Hi maintainers, following up on this PR as it hasn’t had a maintainer review yet. The implementation and local validation are documented above, while the hosted workflows are still waiting for maintainer approval. Could someone approve the workflows and review the PR when convenient? Happy to address any feedback. |
|
Could someone review the hash-collision equality fix when convenient? The workflows still need maintainer approval. |
|
Hi @sylvesterkaczmarek, thank you for your contribution. Unfortunately this repository currently only accepts pull requests from organisation members or approved outside collaborators. Thank you for bringing this bug to our attention. |



Fixes #49.
Compare concrete version types and flattened data instead of hashes. Distinct versions remain separate when hashes collide, and comparisons with unrelated objects return
NotImplemented.Adds regression coverage for collisions, unhashable objects, different version types, private attributes and custom flattening.
Validation:
TZ=UTC python -m unittest discover .: 269 tests passed, including Docker wrappers.python -m mypy concoursetools: passed.