-
Notifications
You must be signed in to change notification settings - Fork 34
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
Not compatible with Click 7.x #16
Comments
Thanks for the kind words! And thanks for testing this - I was thinking that I should try and figure out the lower bound, as it was bound to break at some point. I might have a play to see if we can push compatibility lower (eg. this one looks like we could probably just capture the exception and ignore it..?), but I agree that it's a fairly low priority 👍🏻 |
Can confirm, the Along this line, we also figured out that at least
This particular error is attributable to |
Many thanks both - I have put in simple mechanisms to push support a little further back in history (should now work with click 7.0, rich 10.0) and then pinned the minimum versions for both packages. Let me know if you find any other problems 👍🏻 Phil |
First of all, amazing project! Really loving the look & feel.
I think adoption by the community will be fast as the number of stars is already growing quickly.
I tried out the the package with
Click 7.1.2
and received the following error:It appears this _NumberRangeBase comes from Click 8 onwards.
I think Click 8 has been around long enough for people to adopt it, and compatibility issues to upgrade from 7.x to 8.x are hardly present, it feels fine to me to keep the minimum requirement to be Click 8.0.0.
However, currently there is no lower bound, therefore I'd argue we should set it to
click>8.0
in the requirements to make this more explicit.The text was updated successfully, but these errors were encountered: