Skip to content

Ensure that VersionRange is immutable and hashable - #21

Merged
pombredanne merged 2 commits into
mainfrom
20-hashable
Jan 11, 2022
Merged

Ensure that VersionRange is immutable and hashable#21
pombredanne merged 2 commits into
mainfrom
20-hashable

Conversation

@pombredanne

Copy link
Copy Markdown
Member

See #20
We now ensure that a version_constraints attribute is a tuple

Signed-off-by: Philippe Ombredanne pombredanne@nexb.com

See #20
We now ensure that a `version_constraints` attribute is a tuple 

Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>
@pombredanne
pombredanne requested a review from Hritik14 January 10, 2022 16:27
@Hritik14
Hritik14 force-pushed the 20-hashable branch 3 times, most recently from 8026499 to da3e2ed Compare January 10, 2022 20:08
converters are executed before __attrs_post_init__ thus we need to
convert explicitly in __attrs_post_init__
See: https://www.attrs.org/en/stable/init.html#order-of-execution

Signed-off-by: Hritik Vijay <hritikxx8@gmail.com>
@Hritik14

Copy link
Copy Markdown
Collaborator

@pombredanne Added another commit to resolve the error. Do have a look.

@pombredanne pombredanne left a comment

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM... merging!

@pombredanne
pombredanne merged commit aa2253d into main Jan 11, 2022
@pombredanne
pombredanne deleted the 20-hashable branch January 11, 2022 11:22
@Hritik14 Hritik14 linked an issue Jan 11, 2022 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

VersionRange objects are unhashable

2 participants