Repository navigation
docs: update README for uv and fix stale help sections - #33
Merged
Merged
Conversation
Switch setup instructions from pip to uv (sync/run), update the uv_build version constraint, fix stale pipenv references in help examples, and sync usage lines and option headers with current --help output. Also excludes uv.lock via .gitignore, matching the library convention the maintainer originally chose.
DiddiZ
approved these changes
Mar 9, 2026
Owner
|
Thank you :) |
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.
While setting up the project, I noticed that it already seems to be based on the Astral toolchain and uses
uv.I then went through all described steps, tried them on my machine and updated the documentation as I went along.
Removed a few bumps related to version constraints and
uv.lockshowing up, but not being gitignored.While creating a PDF file for printing, I did notice that the usage description has drifted a bit from the implementation and synced them.
I then tried to optimize image quality to match the DPI of my printer and found that some options do not apply to PDF, so I did a light docs update on that too.
The end result is looking excellent, much higher quality then what I previously got through https://mtgprint.net. Thanks for this nice project!