to avoid 0 padding in Py3.5+ do not truncate#488
Open
jwhitehorn wants to merge 1 commit intoDataBrewery:masterfrom
Open
to avoid 0 padding in Py3.5+ do not truncate#488jwhitehorn wants to merge 1 commit intoDataBrewery:masterfrom
jwhitehorn wants to merge 1 commit intoDataBrewery:masterfrom
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
I noticed this when testing out Cubes - specifically the the Slicer server.
I was running in Python 3.8.1 and noticed that CSVs had many null bytes - lots of them. This was causing all types of problems when loading and parsing these CSV. Upon tracking down the issue I noticed this was the result of calling `truncate on a StringIO stream.
Specifically the docs state:
"Changed in version 3.5: Windows will now zero-fill files when extending."