-
Notifications
You must be signed in to change notification settings - Fork 167
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
Too strict requirement on scipy #570
Comments
I have a PR which changes various dependency versions for support of the latest (Python 3.13) but it will cause a loss of support for Python 3.8 and 3.9 since it requires a recent version of scipy that only supports Python>=3.10. If you can please comment there or submit another PR with versions worked out to your satisfaction. My goal is to support as many versions of Python as possible and for the package to play well with others. I'm no expert at packaging so I'm happy to take suggestions. Thanks in advance, I appreciate your help! |
See #569 |
The version requirements in #569 look fine. Thanks! |
Thanks for looking that over, @lexming |
This requirement on scipy is too strict and makes it hard to package
climate_indices
with other software as it forces this single version of scipy into the environment. Please change it to a minimum version requirement like it is already done for the other requirements:climate_indices/pyproject.toml
Line 49 in 3c50346
On a side note, it would be also convenient to tag the commits that correspond to the versions released on PyPI. Then it would be straightforward to know which commit corresponds to each version and download the corresponding sources from github if needed.
The text was updated successfully, but these errors were encountered: