Repository navigation
Build pandas PDF reports with reusable Python components - #137
Merged
Merged
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.
The pandas guide currently requires an HTML/CSS template. Add a separate component-authoring path using the public Fullbleed 2.6.0a9 wheel and pandas 3.0.6, with a small MIT source kit and actual PDF/HTML downloads.
The fictional 40-row report uses reusable metric components, named style parts, typed styles, DataTable column callbacks, repeated table headers, and finalized page totals. Explain exactly how
class_name,style,styled, andwith_partsapply styling. Both HTML export modes are included with the bundled font and its license. Preserve the existing stable HTML/CSS example and all 1,036 prior tracked assets/example files byte for byte.Validation: the source ZIP rebuilds deterministically and reproduces the published three-page PDF. Saved-PDF checks cover one, three, 40 and 120 rows, long and Unicode values, literal markup, signed currency, missing dates, input immutability, eight rejected CSV cases, and identical sample PDF bytes from a fresh process. Independent readers inspect row completeness/order, repeated headings, page totals, page bounds, and rasterize every page. Strict MkDocs and 142-page link checks pass. Twenty-five real Chrome checks cover desktop/mobile, light/dark mode, six file downloads and both standalone HTML exports; screenshots and PDF pages reviewed.
Normalize source-kit text to LF so Windows checkout settings preserve the exact downloadable archive. Run its multi-command CI step in Bash so a failed archive comparison stops immediately. Add Windows/Linux source-kit checks and a real-browser deployment gate. The API is explicitly experimental. Tagged output and structural checks are not presented as PDF/UA conformance or browser-pagination parity.