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
With the increasing adoption of numpy>=2.0.0, and some prominent packages—such as spaCy—now requiring this version as a dependency (see here), I would like to inquire if there are plans for GluonTS to support numpy>=2.0.0 in the near future.
Our team is actively working on AutoGluon, which relies on both spacy and gluonts. We have been receiving numerous requests from our users to support numpy>=2.0.0. Having compatibility with this version would greatly benefit our project and likely others in the ecosystem.
We would greatly appreciate your consideration of this request and any guidance you could provide on a potential timeline for supporting this upgrade.
Thank you for your continued efforts and support!
References
list reference and related literature
list known implementations
The text was updated successfully, but these errors were encountered:
@suzhoum gluonts 0.16 is released, with support for numpy 2. Closing this for now, feel free to open any issues you may find with it. And thanks for opening the issue!
Description
Hi Team,
With the increasing adoption of numpy>=2.0.0, and some prominent packages—such as spaCy—now requiring this version as a dependency (see here), I would like to inquire if there are plans for GluonTS to support numpy>=2.0.0 in the near future.
Our team is actively working on AutoGluon, which relies on both spacy and gluonts. We have been receiving numerous requests from our users to support numpy>=2.0.0. Having compatibility with this version would greatly benefit our project and likely others in the ecosystem.
We would greatly appreciate your consideration of this request and any guidance you could provide on a potential timeline for supporting this upgrade.
Thank you for your continued efforts and support!
References
The text was updated successfully, but these errors were encountered: