Regexp pattern accepted by --exclude option #16
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
|
@jimbrowne thanks for this...an |
Closed
|
the Regexp patterns are different from those used in rsync right? which simplification from @victorpoluceno are you referring to? |
| # determine if the file should be excluded according to command line arguments. | ||
| excludeFile = False | ||
| for excludePath in exclude: | ||
| if fullpath.startswith(excludePath): |
There was a problem hiding this comment.
this is probably error-prone as it matches all directories that start with (but do not match exactly) the given exclude pattern
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.
This builds on the patch from @NotDaveLane; I've needed to use regexps for excluding files rather than just simple substrings.
Probably want to pull in the simplification from @victorpoluceno as well.