BUG: use compression=None (again) to avoid inferring compression #37909
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jreback
requested changes
Nov 17, 2020
twoertwein
force-pushed
the
compression
branch
from
aac4efe
to
c2f0ff6
Compare
|
@jreback green'ish |
twoertwein
force-pushed
the
compression
branch
from
c2f0ff6
to
eef347b
Compare
|
thanks @twoertwein |
8 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
read_fwfwas usingcompression=Noneto infer compression (in addition tocompression="infer"). This is undocumented but was enforced in a test.In #37639, I thought this was the expected behavior for all functions. That as wrong,
read_csvexplicitly states thatcompression=Nonedoes not infer any compression.