You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Such pinning makes it impossible to integrate this tool into other projects (without hacky workarounds like override-dependencies, forceful dependency overrides). And I assume the intention is to allow such use cases given the existence of py.typed file which otherwise would be redundant.
Hi @Zaczero - thanks for opening the issue. I appreciate the challenges that the strict dependency requirements might impose on using pypgstac within a larger project, but I have not run into that recently. Is there a particular dependency that is causing the problem in your case?
Feel free to open a pull request with the changes you described! It might be fine to open everything up with >= but I suspect there is a reason at least some of them have been pinned to specific versions.
Zaczero
added a commit
to Zaczero/pgstac
that referenced
this issue
Jan 27, 2025
https://github.com/stac-utils/pgstac/blob/main/src/pypgstac/pyproject.toml
Such pinning makes it impossible to integrate this tool into other projects (without hacky workarounds like override-dependencies, forceful dependency overrides). And I assume the intention is to allow such use cases given the existence of py.typed file which otherwise would be redundant.
There exist online resources on this topic: https://discuss.python.org/t/should-i-be-pinning-my-dependencies/13159
A popular and good practice is to use
>=
for defining your dependencies.The text was updated successfully, but these errors were encountered: