-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Python] Compatibility with boto 1.36 #45305
Comments
PyArrow does not depend on boto3. These tests only exercise our fsspec bridge. |
The only matching result in a Google search is aws/aws-sdk-cpp#1337 (comment) , but it doesn't involve boto3 at all... |
Can you post the exception traceback(s)? |
AFAIU there's some optional support; at least, if
Sure: Example FAILURE
Example ERROR
|
So, it's a bit weird that this is surfaced by a boto3 upgrade, but this is a Minio vs. AWS SDK compatibility issue, see upstream aws/aws-sdk-java-v2#5805 and minio/minio#20845 According to minio/minio#20845 (comment) , Minio will be fixed to handle new AWS SDK behavior. |
So in other words, this issue ends up being a consequence of #45304, which itself is a consequence of the minio incompatibility. So once a compatible minio is out, things should go back to normal... |
No, it seems to me that #45304 is a different error. It occurs on a different request (PutObject vs. DeleteObjects) and the error message is different. So we'll have to investigate that one separately. |
Until Minio gets fixed.
Until Minio gets fixed. ### Rationale for this change ### What changes are included in this PR? ### Are these changes tested? ### Are there any user-facing changes? * GitHub Issue: #45305 Authored-by: Antoine Pitrou <[email protected]> Signed-off-by: Antoine Pitrou <[email protected]>
Issue resolved by pull request 45311 |
So #45311 works around this on main, but we still have to decide about how to handle the maintenance branches
|
This is a problem in Minio together with boto3. Most users of PyArrow:
So it would be bizarre to add a boto3 version cap to the PyArrow recipe. |
Actually, even for main, the issue should IMO stay open, until Lines 20 to 22 in a74eb7e
can be removed. I mean, I don't mind opening a separate issue, but this has all the required context already - could someone reopen? |
Well, let's reopen then. |
conda has a concept of |
Well, the test suite here is failing because of an incompatibility between two third-party packages: boto3 and Minio. If Minio is packaged in conda-forge, perhaps its recipe can use the proposed |
FYI cross posting for visibility as I do indeed use PyArrow, S3FS (i.e. boto3) and Minio: fsspec/s3fs#931 |
The failures described below where traced down to minio/minio#20845, which was worked around in #45311.
This issue is now about removing
arrow/ci/conda_env_python.txt
Lines 20 to 22 in a74eb7e
once a compatible minio release has happened .
Previously:
Describe the enhancement requested
Related to but independent from #45304, the following errors appear in the python test suite with boto3 1.36.1 (still with aws-sdk 1.1.458):
Things run fine when constrained to boto3/botocore 1.35.88.
One question from the POV of the feedstock is whether the breakage is bad enough to encode
boto3 <1.36
in the package metadata itself (until this issue is fixed), or whether to just add that constraint to the test requirements. That decision needs to be made for all maintenance branches too (not necessarily in the same way as formain
), which are equally affected.CC @raulcd @pitrou @kou @assignUser
Component(s)
Packaging, Python
The text was updated successfully, but these errors were encountered: