-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Is it possible to loosen the upper-bound constraint on Typer? #11708
Labels
Comments
Thanks for the note! I am not aware of a specific reason for this, but in general we try to avoid overly open version specifications, and we've had some version-related issues with Typer in the past. We'll look into increasing this, but it might take a bit. |
polm
added
third-party
Third-party packages and services
enhancement
Feature requests and improvements
labels
Oct 28, 2022
Merged
3 tasks
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Hi! I'd like to use spaCy in a project where I already used Typer v0.6.2.
I cannot install spaCy because spaCy forces all Typer versions to be the following:
spaCy/requirements.txt
Line 12 in 865691d
I use Poetry as my dependency manager, which means that it will not allow the inclusion of spaCy as a dependency with the constraint, even if I do not want to use the CLI aspect of spaCy.
Is there a reason for limiting Typer to <0.5.0, and is it possible to loosen this constraint?
Thank you!
The text was updated successfully, but these errors were encountered: