[WIP] Add draft support for binary fixed width files #475
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
This is analogous to R's scan() function
|
@johnmyleswhite Is this still relevant or should it be closed? |
|
I think this is fine to close. |
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.
This pull request starts down the path of supporting reading DataFrames from fixed-width files. The current implementation is a barebones implementation of something like R's
scan()function. I still need to write a version that reads fixed-width files in which all entries are plain-text and need type inference.Eventually I'd like to move all of our I/O tools into a separate I/O package. But for now I'd just like to get this tool written.
Please bikeshed the names
readfwfbinandwritefwfbin. I don't like the namescan, but we can definitely do better than the names I've chosen so far.