Open envelio-cb opened 1 month ago
+1 to this! Also in general to not setting upper bounds to package versions unless strictly necessary.
I made a similar comment about this here https://github.com/databricks/databricks-sql-python/issues/427 (similar case that's affecting us but for the pyarrow < 17.0
limitation
+1
I am working on upgrading our ecosystem to use numpy >= 2.0.2 which currently breaks at your package.
Afaik you don't use numpy in your code except for testing. Thus, I am wondering if you can either drop the dependency and add it as dev-only dependency or if you can be less strict in the versioning of numpy and support numpy >= 2.0.2.
Here is also a list of the numpy ecosystem compatibility with numpy 2.0: https://github.com/numpy/numpy/issues/26191
Kind regards