[CI][Python] Use pipx to install GCS testbench in order to decouple version of Python under test #38183
Assignees
Milestone
Comments
5 tasks
pitrou
added a commit
to pitrou/arrow
that referenced
this issue
Aug 27, 2024
pitrou
added a commit
to pitrou/arrow
that referenced
this issue
Aug 27, 2024
pitrou
added a commit
to pitrou/arrow
that referenced
this issue
Aug 27, 2024
pitrou
added a commit
to pitrou/arrow
that referenced
this issue
Aug 28, 2024
kou
pushed a commit
that referenced
this issue
Aug 29, 2024
### Rationale for this change Installing the GCS testbench using the same Python that's being used to test PyArrow is fragile: some testbench versions may not be compatible, or there could be conflicts among the dependencies of the respective libraries. ### What changes are included in this PR? Use `pipx` to install the GCS testbench in a separate, controlled environment, using an appropriate Python version. ### Are these changes tested? Yes, by CI. ### Are there any user-facing changes? No. * GitHub Issue: #38183 Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
|
Issue resolved by pull request 43852 |
mapleFU
pushed a commit
to mapleFU/arrow
that referenced
this issue
Sep 3, 2024
…e#43852) ### Rationale for this change Installing the GCS testbench using the same Python that's being used to test PyArrow is fragile: some testbench versions may not be compatible, or there could be conflicts among the dependencies of the respective libraries. ### What changes are included in this PR? Use `pipx` to install the GCS testbench in a separate, controlled environment, using an appropriate Python version. ### Are these changes tested? Yes, by CI. ### Are there any user-facing changes? No. * GitHub Issue: apache#38183 Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
khwilson
pushed a commit
to khwilson/arrow
that referenced
this issue
Sep 14, 2024
…e#43852) ### Rationale for this change Installing the GCS testbench using the same Python that's being used to test PyArrow is fragile: some testbench versions may not be compatible, or there could be conflicts among the dependencies of the respective libraries. ### What changes are included in this PR? Use `pipx` to install the GCS testbench in a separate, controlled environment, using an appropriate Python version. ### Are these changes tested? Yes, by CI. ### Are there any user-facing changes? No. * GitHub Issue: apache#38183 Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the enhancement requested
When creating the Wheels for Python 3.12 we found a couple of issues around the installation of GCS testbench. One of the problems is we do use the same version of Python we are creating the wheels for than the one we use to install GCS testbench. This causes issues like no wheels available etcetera.
GCS testbench has added the ability to use pipx for the installation: googleapis/storage-testbench#545 (comment)
And as suggested here: #37901 (comment)
we should update our invocations on C++, Python and R tests.
We also should use a specific version of Python that works with the specific GCS testbench being used.
Component(s)
Continuous Integration, Python
The text was updated successfully, but these errors were encountered: