We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As discussed in MIT-LCP/wfdb-python#446 and https://iscinumpy.dev/post/bound-version-constraints/#tldr, setting upper bounds on dependencies is perhaps not a good idea.
Currently most dependencies in https://github.com/MIT-LCP/physionet-build/blob/dev/pyproject.toml are specified with PACKAGE = "^n.n.n". The carat sets an upper bound on the major version.
PACKAGE = "^n.n.n"
We should consider switching these to PACKAGE = ">n.n.n", as we did in MIT-LCP/wfdb-python#448
PACKAGE = ">n.n.n"
The text was updated successfully, but these errors were encountered:
No branches or pull requests
As discussed in MIT-LCP/wfdb-python#446 and https://iscinumpy.dev/post/bound-version-constraints/#tldr, setting upper bounds on dependencies is perhaps not a good idea.
Currently most dependencies in https://github.com/MIT-LCP/physionet-build/blob/dev/pyproject.toml are specified with
PACKAGE = "^n.n.n". The carat sets an upper bound on the major version.We should consider switching these to
PACKAGE = ">n.n.n", as we did in MIT-LCP/wfdb-python#448The text was updated successfully, but these errors were encountered: