-
-
Notifications
You must be signed in to change notification settings - Fork 286
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
Dependencies are rather strict, leading to conflicts #449
Comments
|
|
Hmm, if you're eager to always pin Hatch dependencies to recent versions and not support compatibility hacks, then perhaps it'd be helpful to more prominently recommend installing Hatch via |
Not really, more so eager to enforce fixes or features that directly affect Hatch. I don't set minimum versions arbitrarily 😉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The requirement
packaging>=21.3
makes Hatch impossible to install it alongside Poetry 1.1. (Here the blame is definitely not entirely on Hatch!)Also,
click>=8.0.3
is less than a year old, and occasionally some package may pinclick <8
.Since Hatch is a build tool which may be used in large environments alongside older dependencies, it would in general be nice if its dependencies were left a bit looser, perhaps vendoring newly introduced functionality. Or does Hatch make essential use of these new versions?
The text was updated successfully, but these errors were encountered: