This is an automated email from the ASF dual-hosted git repository.
westonpace pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/arrow.git
The following commit(s) were added to refs/heads/master by this push:
new 5003278 ARROW-13747: [Python][CI] Requiring s3fs >= 2021.8
5003278 is described below
commit 5003278ded77f1ab385425143aafd085fda1f701
Author: Weston Pace <[email protected]>
AuthorDate: Wed Aug 25 12:25:12 2021 -1000
ARROW-13747: [Python][CI] Requiring s3fs >= 2021.8
aiobotocore recently released 1.4.0 which is incompatible with s3fs <
2021.8 (which was also just released). Related:
https://stackoverflow.com/questions/68864939/s3fs-suddenly-stopped-working-in-google-colab-with-error-attributeerror-module
Some nightly builds are failing. Even though conda-forge now has s3fs
2021.8 the builds are caching previous results. This issue should just resolve
itself eventually when the conda/docker caches clear. However, if we want to
force it working again this PR requires the newer version of s3fs.
Closes #11003 from westonpace/bugfix/ARROW-13747-bad-aiobotocore-build
Authored-by: Weston Pace <[email protected]>
Signed-off-by: Weston Pace <[email protected]>
---
ci/conda_env_python.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/ci/conda_env_python.txt b/ci/conda_env_python.txt
index 9124c7e..5f4d4c8 100644
--- a/ci/conda_env_python.txt
+++ b/ci/conda_env_python.txt
@@ -27,6 +27,6 @@ pytest
pytest-faulthandler
pytest-lazy-fixture
pytz
-s3fs>=0.4
+s3fs>=2021.8.0
setuptools
setuptools_scm
