jorisvandenbossche commented on pull request #8834: URL: https://github.com/apache/arrow/pull/8834#issuecomment-740125082
It's definitely a serious annoyance *in the time period between numpy releasing and pyarrow releasing with this fix* (because a plain `pip install pyarrow` will be broken in that period). But once there is a fixed pyarrow, I agree it will probably be OK (then it's only a problem for people upgrading numpy without upgrading pyarrow). Ideally we would have a quick bugfix release, so numpy doesn't need to feel hindered by the pyarrow-numpy compatibility issue in deciding when to do your final release. Reality is though that our release process is unfortunately quite heavy-weight, so the question about timing has to be seen in that light. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
