Post #3720232
2026-06-05 17:42 UTC
@tisba@ruby.social I'm not that experienced with Rust, but in Python (which is fairly similar in this respect AFAIK) I would say you are correct, it's generally useful to make your dependency constraints as broad as possible in the non-lock file. That gives people wanting to install your package the most flexibility to combine it with other things in the same environment.
Of course, if you know your package is not compatible with some version(s) of a dependency, you'd want to indicate that with an appropriate restriction - like, if you use a feature that was added in version 3, you'd restrict the version of that dependency to >=3.
Replies (1)
-
@diazona@techhub.social 2026-06-05 17:45
@tisba@ruby.social P.S. the other end of this spectrum, where you pin your dependencies to require specific versions in a non-lock file, is absolutely horrible to work with if your package is ever installed in an environment along with other things. Bazel does that (or at least used to, I'm not sure if they've moved away from it in the most recent versions) and it has caused me and others a great deal of frustration 😅