-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
[WIP]REGR: Fixed reading from public S3 buckets with credentials #34866
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
Conversation
Closes pandas-dev#34626 This works in 1.0.4 I think, so no whatsnew.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
minor comment otherwise lgtm
@pytest.mark.slow | ||
def test_read_s3_public(): | ||
# ensure we can read from a public bucket with credentials | ||
pytest.importorskip("s3fs") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you use the skip_if_no
decorator from pandas/util/_test_decorators here instead?
Ahh just realised we are looking at the same thing @TomAugspurger . I think the case #34626 is trying to address is reading without AWS Credentials right? I've put a test together for this: #34877 |
The credentials @TomAugspurger is adding here are dummy (non-working) credentials to avoid a moto failure. But: since this is reading from an actual s3, and nothing is being mocked, moto should not be involved here? |
Agree - think it should be as simple as: https://github.com/pandas-dev/pandas/pull/34877/files#diff-681243e864617f600083a270b329d17dR36 - unless i'm missing something? |
I thought the issue was using credentials that are invalid for a public bucket. I don’t know what s3fs’ default behavior is when no credentials are found.
… On Jun 20, 2020, at 04:29, Ali McMaster ***@***.***> wrote:
The credentials @TomAugspurger is adding here are dummy (non-working) credentials to avoid a moto failure. But: since this is reading from an actual s3, and nothing is being mocked, moto should not be involved here?
Agree - think it should be as simple as: https://github.com/pandas-dev/pandas/pull/34877/files#diff-681243e864617f600083a270b329d17dR36 - unless i'm missing something?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
@TomAugspurger - my understanding was:
I think (2) was the regression in #34626 - hence my PR here But also think we should merge the case you are testing here ~ Dummy AWS Creds since maybe that tests (1) here? |
Sounds good. Can you add the tests from my PR and I'll just close mine? Regardless, I think we should wait till #34266 is in. |
Closing in favor of #34877. |
Closes #34626
This works in 1.0.4 I think, so no whatsnew.
I'd like to wait for #34266 to get in first. I'll need to update things.
And in the future, I'd like to deprecate this behavior in favor of something like
It should be easy to detect the cases when we need to do that. We just don't have the
storage_options
kwarg yet.