Fix for pdfcat options parse, issue #70 #71
Merged
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 was meant to fix issue #70 <---- LINK. Is there a way to connect a pull request to an existing issue instead of making a new one? |
mstamy2
added a commit
that referenced
this pull request
Feb 25, 2014
Fix for pdfcat options parse, fix issue #70
polyglot-jones
pushed a commit
to polyglot-jones/PyPDF2
that referenced
this pull request
Aug 11, 2020
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.
nargs=argparse.REMAINDER means just pass the rest of these arguments unparsed. "-2:" works in the right place, not in the wrong place. The --help is still okay (maybe clearer). Errors in the earlier options are still caught by argparse. Later problems are caught in parse_filename_page_ranges(). All seems to be well.