Improve ProgressBar docstring to clarify usage of increments and completion #1456
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.
Summary
This pull request refines the documentation for the
ProgressBar(Protocol)
in_progressbar.py
:Clarifies usage of
n
vs.completed
:n
is generally used for page-based increments.completed
is especially useful for percentage-based tracking.Adds a Short Example:
Expands the Docstrings:
__init__
Rationale
**kwargs
so it won’t break on future OCRmyPDF releases.n
increments andcompleted
values.Testing
Additional Notes