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
Is your feature request related to a problem? Please describe.
Currently when I install the library from pypi, with the current version of numpy greater than 2, pmdarima raises error of binaries incompatibility, this requires users to freeze the numpy to the version greater than 1.21.2 yet less than 2.0.
Should you add bounds to the requirements inplace during the implementation of numpy 2 support #578 this will prevent users from usually handling the version errors manually.
Another issue I noticed when I built the library from source is that the version is fixed to 0.0.0
I understand that you decided to make it default to 0.0.0 for local development and non-tagged commits bumping the version in the __init__ file at every release would be very easy for bug reporting and no confusion for those installing the library from the source.
Describe the solution you'd like
Changing the requirements.txt file with version bounds
Tried this locally and when I added bounds using make develop && make install gave me version less than numpy 2 and when the bound was removed I was getting the latest numpy version.
Describe alternatives you've considered
If this PR #578 could be quickly merged we should not need these requirements modifications.
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently when I install the library from pypi, with the current version of numpy greater than 2,
pmdarima
raises error of binaries incompatibility, this requires users to freeze the numpy to the version greater than1.21.2
yet less than2.0
.Should you add bounds to the requirements inplace during the implementation of
numpy 2
support #578 this will prevent users from usually handling the version errors manually.Another issue I noticed when I built the library from source is that the version is fixed to
0.0.0
I understand that you decided to make it default to
0.0.0
for local development and non-tagged commits bumping the version in the__init__
file at every release would be very easy for bug reporting and no confusion for those installing the library from the source.Describe the solution you'd like
Changing the
requirements.txt
file with version boundspmdarima/requirements.txt
Line 3 in c33a017
numpy>=1.21.2, <2.0
Tried this locally and when I added bounds using
make develop && make install
gave me version less thannumpy 2
and when the bound was removed I was getting the latest numpy version.Describe alternatives you've considered
If this PR #578 could be quickly merged we should not need these requirements modifications.
Additional Context
No response
The text was updated successfully, but these errors were encountered: