-
Notifications
You must be signed in to change notification settings - Fork 21
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
Requirements not aligned with Python versions #139
Comments
@j-c-cook Great catch. Do you see a need to release a fix quickly for this? I can always update the requirement to Python 3.7 and release a If not, I will tag it for |
Given that there is an goodreason to be using However, if we can backtrack to a |
My proposal is to align with the Anaconda distribution for v2.1. For the Python
The latest Coolprop release is still 6.4.1. |
Did you mean to propose 3.8? I tend to not like the idea of going to another version, unless there is a reason. I agree with moving from 3.6->3.7 from pygfunction-v1.x -> pygfunction-2.x respectively for the new additions to scipy that are being used. Looking at the same documentation, but for the Python 3.7 release:
|
I agree with going for Python 3.7. It seems the versions are the same anyways. |
Looking now further into this issue, it seems the requirements was only incorrect in the README.md file: Lines 44 to 54 in 0e67d4e
The setup.py file correctly shows: Lines 9 to 18 in 0e67d4e
Line 37 in 0e67d4e
|
Looks like you're right. I had seen it on PyPI, and it does look like it was only the README. |
Pygfunction-2.0.0 has a
scipy>=1.6.2
requirement. The minimum allowable Python version in that scipy release was Python 3.7 https://pypi.org/project/scipy/1.6.2/.The text was updated successfully, but these errors were encountered: