glob.raw_escape.pathlib issue with inheritance on Python versions greater than 3.12.EXTMATCH case with !(...) patterns.wcmatch.glob.pathlib changes).glob pattern list.exclude option to fnmatch, pathlib, and glob methods that allows exclusion patterns to be specified directly without needing to enable NEGATE and prepend patterns with !. exclude accepts a separate pattern or pattern list. exclude should not be used in conjunction with NEGATE. One or the other should be used.dir_fd in glob patterns.pathlib.fnmatch.translate no longer requires user to normalize their Windows paths for comparison. Previously, portions of the translate regex handled both / and \\, while other portions did not. This inconsistent handling forced users to normalize paths for reliable matching. Now all of the generated regex should handle both / and \\.is_magic function to the glob and fnmatch library.fnmatch now has escape available via its API. The fnmatch variant uses filename logic instead of path logic.raw_escape in glob as it is very niche and the same can be accomplished simply by using codecs.decode(string, 'unicode_escape') and then using escape.os.fspath to convert path-like objects to string/bytes, whatever the return from __fspath__ is what Wildcard Match will accept. Don't try to convert paths via __str__ or __bytes__ as not all path-like objects may implement both.str or bytes.bracex's ability to abort parsing on extremely large pattern expansions. Patterns like {1..10000000} will now abort dramatically quicker. Require bracex 2.1.1 which aborts much quicker.[:alpha:] range.WcMatch's on_init hook now only accepts kwargs and not args.__init__ parameter as root_dir instead of base. This is to make it more clear when we are talking about the overall root directory that all paths are relative to vs the base path of a file which is relative to the root directory and the actual file name.WcMatch changed from base to _root_dir. This attribute is not really meant to be referenced by users and as been marked as private.backrefs and update documentation to note that POSIX properties never actually enabled the use of Unicode properties. While the documentation stated this and it was probably intended, it was never actually enabled. Currently, Wildcard match has chosen to keep with the ASCII definition for now as it has been since the feature was introduced. This may change in the future if there is demand for it.[:word:] POSIX character class.NODIR pattern looks at both / and \\ on Windows.EXTGLOB/EXTMATCH groups in the returned regular expression patterns.REALPATH that all symlinks are evaluated.Check out Release Notes to learn more about upgrading to 7.0.
SPLIT and BRACE which requires a user to escape {, } and | to avoid expanding a pattern.raw_escape now accepts the raw_chars parameter so that translation of Python character back references can be disabled.scandir will not return . and .. for wildcard patterns that require iterating over a directory to match the files against a pattern. This matches Python's glob and is most likely what most users expect. Pattern matching logic is unaffected.SCANDOTDIR flag to enable previous behavior of injecting . and .. in scandir results. SCANDOTDIR has no affect on match functions such as globmatch which don't use directory scanning.NODOTDIR has been added to disable patterns such as .* from matching . and ... When enabled, matching logic is changed to require a literal pattern of . and .. to match the special directories . and ... This is more Zsh like.!(...)) incorrectly allowed for hidden files to be returned when one of the subpatterns started with ., even when DOTMATCH/DOTGLOB was not enabled.NOUNIQUE is enabled and pathlib is being used, you could still get non-unique results across patterns expanded with BRACE or SPLIT (or even by simply providing a list of patterns). Ensure that unique results are only returned when NOUNIQUE is not enabled.escape and raw_escape with back slashes.globmatch does not match test// with pattern test/*.pathlib.match should not evaluate symlinks that are on the left hand side of what was matched.EXTMATCH/EXTGLOB can now be used with NEGATE without needing MINUSNEGATE. If a pattern starts with !(, and NEGATE and EXTMATCH/EXTGLOB are both enabled, the pattern will not be treated as a NEGATE pattern (even if !( doesn't yield a valid EXTGLOB pattern). To negate a pattern that starts with a literal (, you must escape the bracket: !\(.glob to be consistent with other functions.FOLLOW and GLOBSTAR were used, a pattern like **/* would not properly match a directory which was a symlink. While Bash does not return a symlinked folder with **, * (and other patterns), should properly find the symlinked directory.pathlib clearly states that the match method, if the pattern is relative, matches from the right. Wildcard Match used the same implementation that rglob used, which prepends **/ to a relative pattern. This is essentially like MATCHBASE, but allows for multiple directory levels. This means that dot files (and special folders such as . and ..) on the left side could prevent the path from matching depending on flags that were set. match will now be evaluated in such a way as to give the same right to left matching feel that Python's pathlib uses.GLOBSTAR. Recursive directory search should return all dot files, which should then be filtered by the patterns. They should not be excluded before being filtered by the pattern.GLOBTILDE flag.glob by default now returns only unique results, regardless of whether multiple patterns that match the same file were provided, or even when BRACE or SPLIT expansion produces new patterns that match the same file.NOUNIQUE has been added that makes glob act like Bash, which will return the same file multiple times if multiple patterns match it, whether provided directly or due to the result of BRACE or SPLIT expansion.limit parameter in related API functions.WcMatch class crawls the file system, it utilizes the aforementioned matching functions in it's operation, and indirectly takes advantage of this. glob (and related functions: rglob, iglob, etc.) will also filter redundant patterns except when NOUNIQUE is enabled, this is so they can better act like Bash when NOUNIQUE is enabled.BRACE is now processed before SPLIT in order to fix a number of edge cases.RAWCHARS was inconsistently applied at different times depending on what was calling it. It is now applied first followed by BRACE, SPLIT, and finally GLOBTILDE.glob related functions (except in pathlib) called root_dir that allows a user to specify a different working directory with either a string or path-like object. Path-like inputs are only supported on Python 3.6+.globmatch and globfilter path inputs. Path-like inputs are only supported on Python 3.6+.glob relative path handling so internally it is indistinguishable from when it is given no relative path and uses the current working directory. This fixes an issue where pathlib couldn't handle negate patterns properly (!negate).GLOBSTAR pattern, followed by a slash, was not disabling MATCHBASE.pathlib relative path resolution in glob implementations.glob, avoid using up too many file descriptors by acquiring all file/folder names under a directory in one batch before recursing into other folders.wcmatch.pathlib which contains pathlib variants that uses wcmatch.glob instead of the default Python glob.escape and raw_escape can manually be forced to use Windows or Linux/Unix logic via the keyword only argument by setting to False or True respectively. The default is None which will auto detect the system.FORCECASE has now been removed.globsplit and fnsplit have been removed.version and version_info have been removed.glob.glob would mistakenly abort if a pattern started with a literal file or directory and could not match a file or directory. This caused subsequent patterns in the chain to not get evaluated.CASE flag which allows for case sensitive paths on Linux, macOS, and Windows. Windows drive letters and UNC //host-name/share-name/ portion are still treated insensitively, but all directories will be treated with case sensitivity.CASE and FORCEUNIX, FORCECASE is no longer needed. Deprecate FORCECASE which will be removed at some future point.FORCEWIN and FORCEUNIX to force Windows or Linux/Unix path logic on commands that do not access the file system: translate, fnmatch, filter, globmatch, globfilter, etc. These flags will not work with glob, iglob or with the WcMatch class. It also will not work when using the REALPATH flag with things like fnmatch, filter, globmatch, globfilter.glob corner case where the first folder, if defined as a literal name (not a magic pattern), would not be treated properly if IGNORECASE was enabled in Linux.WcMatch.is_aborted.kill and reset in WcMatch. There are legitimate reasons to not deprecate killing via kill instead of simply breaking.glob.NODIR patterns exclude if matched not exclude if not matched.WcMatch class methods kill and reset. WcMatch should be broken with a simple break statement instead.MARK to force glob to return directories with a trailing slash.MATCHBASE that causes glob glob related functions and WcMatch, when the pattern has no slashes in it, to seek for any file anywhere in the tree with a matching basename.NODIR that causes glob matchers and crawlers to only match and return files.NEGATE) now always enable DOTALL in the exclusion patterns. They also will match symlinks in ** patterns. Only non NEGATE patterns that are paired with a NEGATE pattern are subject to symlinks and dot rules. Exclusion patterns themselves allow dots and symlinks to make filtering easier.SPLIT flag and provide an inclusion pattern with your default ('default_pattern|!exclusion'), or feed in a list of multiple patterns instead of a single string (['inclusion', '!exclusion']). If you really need the old behavior, you can use the NEGATEALL flag which will provide a default inclusion pattern that matches all files.glob should not match slashes.glob on Linux or macOS.glob command would use GLOBSTAR logic on ** even when GLOBSTAR was disabled.WcMatch class, defer hidden file check until after the file or directory is compared against patterns to potentially avoid calling hidden if the pattern doesn't match. The reduced lstat calls improve performance.globsplit and fnsplit have been deprecated. Users are encouraged to use the new SPLIT flag to allow functions to use multiple wildcard paths delimited by |.globmatch and globfilter will now parse provided paths as real paths if the new REALPATH flag is set. This has the advantage of allowing the commands to be aware of symlinks and properly apply related logic (whether to follow the links or not). It also helps to clarify ambiguous cases where it isn't clear if a file path references a directory because the trailing slash was omitted. It also allows the command to be aware of Windows drives evaluate the path in proper context compared to the current working directory.WcMatch class no longer accepts the recursive or show_hidden parameter, instead the RECURSIVE or HIDDEN flag must be used.WcMatch class now can search symlink directories with the new SYMLINK flag.glob and iglob functions now behave like Bash 5.0 in regards to symlinks in GLOBSTAR (**). GLOBSTAR will ignore symlink directories. This affects other functions such as globmatch and globfilter when the REALPATH flag is enabled.FOLLOW was added to force related glob commands to recognize and follow symlink directories.glob regression where inverse patterns such as !**/test/** would allow a directory base/test to match when it should have excluded it.glob should handle root paths (/) properly, and on Windows, it should assume the drive of the current working directory.EXTMATCH/EXTGLOB should allow literal dots and should not treat dots like sequences do.!(...) extended match patterns in glob and globmatch so that they properly match . and .. if their pattern starts with ..!(...) extended match patterns so that they handle path separators correctly.? or [.] should not trigger matching directories . and .. in glob and globmatch.version and version_info in favor of the more standard __version__ and __version_info__.GLOBSTAR regular expression pattern issues.glob, properly handle files in the current working directory when give a literal pattern that matches it.wcmatch override events (on_error and on_skip) should verify the return is not None and not not falsy.Breaking Changes
Version 2.0 introduces breaking changes in regards to flags. This is meant to bring about consistency amongst the provided libraries. Flag names have been changed in some cases, and logic has been inverted in some cases.
NOBRACE, NOGLOBSTAR, and NOEXTGLOB flags are now BRACE, GLOBSTAR, and EXTGLOB and now enable the features instead of disabling the features. This logic matches the provided fnmatch and wcmatch.DOTGLOB and EXTGLOB also have the respective aliases DOTMATCH and EXTMATCH to provide consistent flags across provided libraries, but the GLOB variants that match Bash's feature names can still be used.fnmatch's PERIOD flag has been replaced with DOTMATCH with inverted logic from what was originally provided.FORCECASE → F, etc.EXTMATCH, but internally it was actually EXTGLOB, this was a bug though. EXTMATCH is now the documented and the actual flag to use.glob that have a directory preceding ** but also end with ** returns the preceding directory.[[:ascii:]-z] should convert to [\x00-\x7f\\-b] not [\x00-\x7f-b].'*' was assumed, now it is '', and if '' is used, all files will be matched. This works better for when full path is enabled as you get the same file matching logic.GLOBSTARLONG which adds support for the Zsh style *** which acts like ** with GLOBSTAR but but traverses symlinks.pathlib.match will respect symlink rules (when the REALPATH flag is given). Hidden file rules will be respected at all times. Enable DOTALL to match hidden files.GLOBSTAR is enabled unless FOLLOW is also enabled, but they should still be matched. Prior to this change, symlinks were not traversed and they were ignored from matching which contradicts how Bash works and could be confusing to users.globmatch and symlink handling when REALPATH is enabled.glob.raw_escape.pathlib issue with inheritance on Python versions greater than 3.12.EXTMATCH case with !(...) patterns.wcmatch.glob.pathlib changes).glob pattern list.exclude option to fnmatch, pathlib, and glob methods that allows exclusion patterns to be specified directly without needing to enable NEGATE and prepend patterns with !. exclude accepts a separate pattern or pattern list. exclude should not be used in conjunction with NEGATE. One or the other should be used.dir_fd in glob patterns.pathlib.fnmatch.translate no longer requires user to normalize their Windows paths for comparison. Previously, portions of the translate regex handled both / and \\, while other portions did not. This inconsistent handling forced users to normalize paths for reliable matching. Now all of the generated regex should handle both / and \\.is_magic function to the glob and fnmatch library.fnmatch now has escape available via its API. The fnmatch variant uses filename logic instead of path logic.raw_escape in glob as it is very niche and the same can be accomplished simply by using codecs.decode(string, 'unicode_escape') and then using escape.os.fspath to convert path-like objects to string/bytes, whatever the return from __fspath__ is what Wildcard Match will accept. Don't try to convert paths via __str__ or __bytes__ as not all path-like objects may implement both.str or bytes.bracex's ability to abort parsing on extremely large pattern expansions. Patterns like {1..10000000} will now abort dramatically quicker. Require bracex 2.1.1 which aborts much quicker.[:alpha:] range.WcMatch's on_init hook now only accepts kwargs and not args.__init__ parameter as root_dir instead of base. This is to make it more clear when we are talking about the overall root directory that all paths are relative to vs the base path of a file which is relative to the root directory and the actual file name.WcMatch changed from base to _root_dir. This attribute is not really meant to be referenced by users and as been marked as private.backrefs and update documentation to note that POSIX properties never actually enabled the use of Unicode properties. While the documentation stated this and it was probably intended, it was never actually enabled. Currently, Wildcard match has chosen to keep with the ASCII definition for now as it has been since the feature was introduced. This may change in the future if there is demand for it.[:word:] POSIX character class.NODIR pattern looks at both / and \\ on Windows.EXTGLOB/EXTMATCH groups in the returned regular expression patterns.REALPATH that all symlinks are evaluated.Check out Release Notes to learn more about upgrading to 7.0.
SPLIT and BRACE which requires a user to escape {, } and | to avoid expanding a pattern.raw_escape now accepts the raw_chars parameter so that translation of Python character back references can be disabled.scandir will not return . and .. for wildcard patterns that require iterating over a directory to match the files against a pattern. This matches Python's glob and is most likely what most users expect. Pattern matching logic is unaffected.SCANDOTDIR flag to enable previous behavior of injecting . and .. in scandir results. SCANDOTDIR has no affect on match functions such as globmatch which don't use directory scanning.NODOTDIR has been added to disable patterns such as .* from matching . and ... When enabled, matching logic is changed to require a literal pattern of . and .. to match the special directories . and ... This is more Zsh like.!(...)) incorrectly allowed for hidden files to be returned when one of the subpatterns started with ., even when DOTMATCH/DOTGLOB was not enabled.NOUNIQUE is enabled and pathlib is being used, you could still get non-unique results across patterns expanded with BRACE or SPLIT (or even by simply providing a list of patterns). Ensure that unique results are only returned when NOUNIQUE is not enabled.escape and raw_escape with back slashes.globmatch does not match test// with pattern test/*.pathlib.match should not evaluate symlinks that are on the left hand side of what was matched.EXTMATCH/EXTGLOB can now be used with NEGATE without needing MINUSNEGATE. If a pattern starts with !(, and NEGATE and EXTMATCH/EXTGLOB are both enabled, the pattern will not be treated as a NEGATE pattern (even if !( doesn't yield a valid EXTGLOB pattern). To negate a pattern that starts with a literal (, you must escape the bracket: !\(.glob to be consistent with other functions.FOLLOW and GLOBSTAR were used, a pattern like **/* would not properly match a directory which was a symlink. While Bash does not return a symlinked folder with **, * (and other patterns), should properly find the symlinked directory.pathlib clearly states that the match method, if the pattern is relative, matches from the right. Wildcard Match used the same implementation that rglob used, which prepends **/ to a relative pattern. This is essentially like MATCHBASE, but allows for multiple directory levels. This means that dot files (and special folders such as . and ..) on the left side could prevent the path from matching depending on flags that were set. match will now be evaluated in such a way as to give the same right to left matching feel that Python's pathlib uses.GLOBSTAR. Recursive directory search should return all dot files, which should then be filtered by the patterns. They should not be excluded before being filtered by the pattern.GLOBTILDE flag.glob by default now returns only unique results, regardless of whether multiple patterns that match the same file were provided, or even when BRACE or SPLIT expansion produces new patterns that match the same file.NOUNIQUE has been added that makes glob act like Bash, which will return the same file multiple times if multiple patterns match it, whether provided directly or due to the result of BRACE or SPLIT expansion.limit parameter in related API functions.WcMatch class crawls the file system, it utilizes the aforementioned matching functions in it's operation, and indirectly takes advantage of this. glob (and related functions: rglob, iglob, etc.) will also filter redundant patterns except when NOUNIQUE is enabled, this is so they can better act like Bash when NOUNIQUE is enabled.BRACE is now processed before SPLIT in order to fix a number of edge cases.RAWCHARS was inconsistently applied at different times depending on what was calling it. It is now applied first followed by BRACE, SPLIT, and finally GLOBTILDE.glob related functions (except in pathlib) called root_dir that allows a user to specify a different working directory with either a string or path-like object. Path-like inputs are only supported on Python 3.6+.globmatch and globfilter path inputs. Path-like inputs are only supported on Python 3.6+.glob relative path handling so internally it is indistinguishable from when it is given no relative path and uses the current working directory. This fixes an issue where pathlib couldn't handle negate patterns properly (!negate).GLOBSTAR pattern, followed by a slash, was not disabling MATCHBASE.pathlib relative path resolution in glob implementations.glob, avoid using up too many file descriptors by acquiring all file/folder names under a directory in one batch before recursing into other folders.wcmatch.pathlib which contains pathlib variants that uses wcmatch.glob instead of the default Python glob.escape and raw_escape can manually be forced to use Windows or Linux/Unix logic via the keyword only argument by setting to False or True respectively. The default is None which will auto detect the system.FORCECASE has now been removed.globsplit and fnsplit have been removed.version and version_info have been removed.glob.glob would mistakenly abort if a pattern started with a literal file or directory and could not match a file or directory. This caused subsequent patterns in the chain to not get evaluated.CASE flag which allows for case sensitive paths on Linux, macOS, and Windows. Windows drive letters and UNC //host-name/share-name/ portion are still treated insensitively, but all directories will be treated with case sensitivity.CASE and FORCEUNIX, FORCECASE is no longer needed. Deprecate FORCECASE which will be removed at some future point.FORCEWIN and FORCEUNIX to force Windows or Linux/Unix path logic on commands that do not access the file system: translate, fnmatch, filter, globmatch, globfilter, etc. These flags will not work with glob, iglob or with the WcMatch class. It also will not work when using the REALPATH flag with things like fnmatch, filter, globmatch, globfilter.glob corner case where the first folder, if defined as a literal name (not a magic pattern), would not be treated properly if IGNORECASE was enabled in Linux.WcMatch.is_aborted.kill and reset in WcMatch. There are legitimate reasons to not deprecate killing via kill instead of simply breaking.glob.NODIR patterns exclude if matched not exclude if not matched.WcMatch class methods kill and reset. WcMatch should be broken with a simple break statement instead.MARK to force glob to return directories with a trailing slash.MATCHBASE that causes glob glob related functions and WcMatch, when the pattern has no slashes in it, to seek for any file anywhere in the tree with a matching basename.NODIR that causes glob matchers and crawlers to only match and return files.NEGATE) now always enable DOTALL in the exclusion patterns. They also will match symlinks in ** patterns. Only non NEGATE patterns that are paired with a NEGATE pattern are subject to symlinks and dot rules. Exclusion patterns themselves allow dots and symlinks to make filtering easier.SPLIT flag and provide an inclusion pattern with your default ('default_pattern|!exclusion'), or feed in a list of multiple patterns instead of a single string (['inclusion', '!exclusion']). If you really need the old behavior, you can use the NEGATEALL flag which will provide a default inclusion pattern that matches all files.glob should not match slashes.glob on Linux or macOS.glob command would use GLOBSTAR logic on ** even when GLOBSTAR was disabled.WcMatch class, defer hidden file check until after the file or directory is compared against patterns to potentially avoid calling hidden if the pattern doesn't match. The reduced lstat calls improve performance.globsplit and fnsplit have been deprecated. Users are encouraged to use the new SPLIT flag to allow functions to use multiple wildcard paths delimited by |.globmatch and globfilter will now parse provided paths as real paths if the new REALPATH flag is set. This has the advantage of allowing the commands to be aware of symlinks and properly apply related logic (whether to follow the links or not). It also helps to clarify ambiguous cases where it isn't clear if a file path references a directory because the trailing slash was omitted. It also allows the command to be aware of Windows drives evaluate the path in proper context compared to the current working directory.WcMatch class no longer accepts the recursive or show_hidden parameter, instead the RECURSIVE or HIDDEN flag must be used.WcMatch class now can search symlink directories with the new SYMLINK flag.glob and iglob functions now behave like Bash 5.0 in regards to symlinks in GLOBSTAR (**). GLOBSTAR will ignore symlink directories. This affects other functions such as globmatch and globfilter when the REALPATH flag is enabled.FOLLOW was added to force related glob commands to recognize and follow symlink directories.glob regression where inverse patterns such as !**/test/** would allow a directory base/test to match when it should have excluded it.glob should handle root paths (/) properly, and on Windows, it should assume the drive of the current working directory.EXTMATCH/EXTGLOB should allow literal dots and should not treat dots like sequences do.!(...) extended match patterns in glob and globmatch so that they properly match . and .. if their pattern starts with ..!(...) extended match patterns so that they handle path separators correctly.? or [.] should not trigger matching directories . and .. in glob and globmatch.version and version_info in favor of the more standard __version__ and __version_info__.GLOBSTAR regular expression pattern issues.glob, properly handle files in the current working directory when give a literal pattern that matches it.wcmatch override events (on_error and on_skip) should verify the return is not None and not not falsy.Breaking Changes
Version 2.0 introduces breaking changes in regards to flags. This is meant to bring about consistency amongst the provided libraries. Flag names have been changed in some cases, and logic has been inverted in some cases.
NOBRACE, NOGLOBSTAR, and NOEXTGLOB flags are now BRACE, GLOBSTAR, and EXTGLOB and now enable the features instead of disabling the features. This logic matches the provided fnmatch and wcmatch.DOTGLOB and EXTGLOB also have the respective aliases DOTMATCH and EXTMATCH to provide consistent flags across provided libraries, but the GLOB variants that match Bash's feature names can still be used.fnmatch's PERIOD flag has been replaced with DOTMATCH with inverted logic from what was originally provided.FORCECASE → F, etc.EXTMATCH, but internally it was actually EXTGLOB, this was a bug though. EXTMATCH is now the documented and the actual flag to use.glob that have a directory preceding ** but also end with ** returns the preceding directory.[[:ascii:]-z] should convert to [\x00-\x7f\\-b] not [\x00-\x7f-b].'*' was assumed, now it is '', and if '' is used, all files will be matched. This works better for when full path is enabled as you get the same file matching logic.Open source projects take time and money. Help support the project by becoming a sponsor. You can add your support at any tier you feel comfortable with. No amount is too little. We also accept one time contributions via PayPal.
Please read the documentation and search the issue tracker to try and find the answer to your question before posting an issue.
When creating an issue on the repository, please provide as much info as possible:
The more info provided, the greater the chance someone will take the time to answer, implement, or fix the issue.
Be prepared to answer questions and provide additional information if required. Issues in which the creator refuses to respond to follow up questions will be marked as stale and closed.
Take part in reviewing pull requests and/or reviewing direct commits. Make suggestions to improve the code and discuss solutions to overcome weakness in the algorithm.
Take time and answer questions and offer suggestions to people who've created issues in the issue tracker. Often people will have questions that you might have an answer for. Or maybe you know how to help them accomplish a specific task they are asking about. Feel free to share your experience to help others out.
Pull requests are welcome, and a great way to help fix bugs and add new features.
A ton of time has been spent not only creating and supporting this tool and related extensions, but also spent making this documentation. If you feel it is still lacking, show your appreciation for the tool and/or extensions by helping to improve the documentation.
Open source projects take time and money. Help support the project by becoming a sponsor. You can add your support at any tier you feel comfortable with. No amount is too little. We also accept one time contributions via PayPal.
Please read the documentation and search the issue tracker to try and find the answer to your question before posting an issue.
When creating an issue on the repository, please provide as much info as possible:
The more info provided, the greater the chance someone will take the time to answer, implement, or fix the issue.
Be prepared to answer questions and provide additional information if required. Issues in which the creator refuses to respond to follow up questions will be marked as stale and closed.
Take part in reviewing pull requests and/or reviewing direct commits. Make suggestions to improve the code and discuss solutions to overcome weakness in the algorithm.
Take time and answer questions and offer suggestions to people who've created issues in the issue tracker. Often people will have questions that you might have an answer for. Or maybe you know how to help them accomplish a specific task they are asking about. Feel free to share your experience to help others out.
Pull requests are welcome, and a great way to help fix bugs and add new features.
A ton of time has been spent not only creating and supporting this tool and related extensions, but also spent making this documentation. If you feel it is still lacking, show your appreciation for the tool and/or extensions by helping to improve the documentation.
MIT License
Copyright © 2018 - 2024 Isaac Muse
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
MIT License
Copyright © 2018 - 2024 Isaac Muse
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Notable changes are minor and will affect very few. This should clarify breaking changes and how to migrate if applicable.
WcMatch class Initialization HookThe WcMatch class on_init hook was cleaned up. Prior to 8.0, it accepted both *args and **kwargs which is quite difficult to maintain and honestly for users to use.
Moving forward, the WcMatch class will restrict all parameters to **kwargs. If you are using the on_init hook, you will simply need to change your override to accept arguments as **kwargs:
# Excplicitly named
+ Release Notes - Wildcard Match Documentation Release Notes
Upgrade to 8.0
Notable changes are minor and will affect very few. This should clarify breaking changes and how to migrate if applicable.
WcMatch class Initialization Hook
The WcMatch class on_init hook was cleaned up. Prior to 8.0, it accepted both *args and **kwargs which is quite difficult to maintain and honestly for users to use.
Moving forward, the WcMatch class will restrict all parameters to **kwargs. If you are using the on_init hook, you will simply need to change your override to accept arguments as **kwargs:
# Excplicitly named
def on_init(self, key1=value, key2=value):
# Or just use `**kwargs`
@@ -68,4 +68,4 @@
[PosixPath('docs/src')]
>>> list(pathlib.Path('.').glob(['docs/./src', 'docs/src/.', 'docs/src'], flags=pathlib.NOUNIQUE))
[PosixPath('docs/src'), PosixPath('docs/src'), PosixPath('docs/src')]
-
\ No newline at end of file
+