Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure that VersionRange is immutable and hashable #21

Merged
merged 2 commits into from
Jan 11, 2022
Merged

Conversation

pombredanne
Copy link
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>
@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
Collaborator

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

Copy link
Member Author

@pombredanne pombredanne left a comment

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