We test different minor versions for pandas because our special usage of pandas in the DataFrame API leads to breakages even between minor versions. In the case of pyarrow, every release is a major version, which is meant to communicate that the API can change (https://arrow.apache.org/docs/format/Versioning.html).
We need to investigate if pytorch commonly make changes that will break us between minor versions.
How will we keep this up to date as new version of pytorch come out?
Imported from Jira BEAM-14353. Original Jira may contain additional context.
Reported by: yeandy.
Subtask of issue #21435
Unable to assign user @yeandy. If able, self-assign, otherwise tag @damccorm so that he can assign you. Because of GitHub's spam prevention system, your activity is required to enable assignment in this repo.
We test different minor versions for pandas because our special usage of pandas in the DataFrame API leads to breakages even between minor versions. In the case of pyarrow, every release is a major version, which is meant to communicate that the API can change (https://arrow.apache.org/docs/format/Versioning.html).
We need to investigate if pytorch commonly make changes that will break us between minor versions.
How will we keep this up to date as new version of pytorch come out?
Imported from Jira BEAM-14353. Original Jira may contain additional context. Reported by: yeandy. Subtask of issue #21435