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
This happens because the pinned version of numpy (1.21.5) is too old - the latest version of numpy is 1.25.1.
There are 2 different ways to fix the problem:
Keep up with the future
This is what I do on development code and it's my recommendation.
Since this project is in an early development phase, I would suggest not pinning any version aside from python>=3.8 and using the latest releases of the required dependencies.
Only if there is a bug upstream for a dependency its version should be pinned.
I tested this and it works, but there are not enough tests in this project to be sure of the consequences.
lazy solution
requires-python = ">=3.8<3.11"
this might be more stable, but has the drawback that you will never be forced to use the latest performance features so you might lose the possibility to make the code faster and/or easier to read and maintain
Considering that you are not working on or maintaining a release branch, I would go for solution 1.
Whatever the choice, I am able to fix this issue with a PR if you want.
The text was updated successfully, but these errors were encountered:
This happens because the pinned version of numpy (1.21.5) is too old - the latest version of numpy is 1.25.1.
There are 2 different ways to fix the problem:
Keep up with the future
This is what I do on development code and it's my recommendation.
Since this project is in an early development phase, I would suggest not pinning any version aside from python>=3.8 and using the latest releases of the required dependencies.
Only if there is a bug upstream for a dependency its version should be pinned.
I tested this and it works, but there are not enough tests in this project to be sure of the consequences.
lazy solution
requires-python = ">=3.8<3.11"
this might be more stable, but has the drawback that you will never be forced to use the latest performance features so you might lose the possibility to make the code faster and/or easier to read and maintain
Considering that you are not working on or maintaining a release branch, I would go for solution 1.
Whatever the choice, I am able to fix this issue with a PR if you want.
The text was updated successfully, but these errors were encountered: