Repository navigation
Conversation
Test data now keeps its bytes, restoring the line-ending fixtures git had normalised.
Record each column's cell types and formats, verify a file by its bytes or cells, and check row-level actions against the data source's row count.
Feed the parser lines matched from the decoded text, and keep the derived table for the first get_data, so a derive reads the file once.
Install all extras in the workflow, and skip the PDF tests where pdfplumber is missing.
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
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.
Every format is read into one grid of cells and a safe table under whyqd's own dialect: CSV with its encoding ladder, Excel cell by cell, PDF, Parquet, and Feather. Each column is profiled, and each source is fingerprinted by its bytes and its cells.
The 1.x read is frozen in
whyqd/parsers/v1.py, so every stored 1.x checksum still verifies. A 2.0 schema carries no row count; row-level actions are checked against the data source's row count. A derive reads its file once.