Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
ENH Recognize 's3n' and 's3a' as an S3 address #11071
+19
−2
Conversation
jreback
commented on an outdated diff
Sep 12, 2015
| @@ -4246,6 +4246,15 @@ def test_parse_public_s3_bucket(self): | ||
| tm.assert_frame_equal(pd.read_csv(tm.get_data_path('tips.csv')), df) | ||
| @tm.network | ||
| + def test_parse_public_s3n_bucket(self): | ||
| + # Read from AWS s3 as "s3n" URL | ||
| + import nose.tools as nt | ||
| + df = pd.read_csv('s3n://nyqpug/tips.csv', nrows=10) | ||
| + nt.assert_true(isinstance(df, pd.DataFrame)) |
|
|
stephen-hoover
changed the title from
ENH Recognize 's3n' as an S3 address to ENH Recognize 's3n' and 's3a' as an S3 address
Sep 12, 2015
stephen-hoover
commented
Sep 12, 2015
|
Fixed. I also realized (reading the links I added for issue #11070 ) that "s3a" is a valid S3 designator as well, so I added that too. |
stephen-hoover
commented
Sep 12, 2015
|
The one test failure appears unrelated to the code change in this PR:
|
|
no it's just hitting the actual error there |
jreback
added the
Data IO
label
Sep 12, 2015
stephen-hoover
referenced
this pull request
Sep 12, 2015
Closed
Improvements for read_csv from AWS S3 #11070
|
add a whatsnew note in 0.17.0 (enhancements section) |
jreback
added this to the
0.17.0
milestone
Sep 13, 2015
stephen-hoover
commented
Sep 14, 2015
|
@jreback , green here too! |
jreback
added a commit
that referenced
this pull request
Sep 14, 2015
|
|
jreback |
95110ac
|
jreback
merged commit 95110ac
into pandas-dev:master
Sep 14, 2015
1 check passed
continuous-integration/travis-ci/pr
The Travis CI build passed
Details
|
thanks! |
stephen-hoover
deleted the
stephen-hoover:recognize-s3n branch
Sep 14, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
stephen-hoover commentedSep 12, 2015
This PR allows
read_csvto recognize that "s3n://" designates a valid AWS S3 address. Partially addresses issue #11070 .