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
Now that pyarrow 2.0 is released, it will get picked by the CI builds that don't pin the pyarrow version. It would be good to pin some builds to use pyarrow 1.0.
I don't think it needs to be based on what is failing (because all builds should be passing right now?). Based on the table at #35259 (comment), there are now 4 envs that have 1.0. We could for example leave 2 of them at "latest version", and pin 2 (or 1) of them to pyarrow 1.0 ?
Now that pyarrow 2.0 is released, it will get picked by the CI builds that don't pin the pyarrow version. It would be good to pin some builds to use pyarrow 1.0.
See this overview table of @simonjayhawkins at #35259 (comment)
The text was updated successfully, but these errors were encountered: