You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First thanks for this wonderful doublestar glob, it makes file matching very easy.
A possible bug we encountered in our usage of doublestar.Glob:
When a file has its name starting with "【" ( Lenticular bracket wikipedia , ulookup ) it doesnt seem to match. Having the "【" in the path or in the filename but not as first character the file matches.
Hi @bnkai - I'm really sorry this took so long for me to get to! I intended on taking a look last weekend, but, before I knew it, the weekend was over!
Anyway, thank you for the well-written bug report! I think I've found the issue and just cut a v1.3.1. I've also included a test case for this issue that seems to be passing. Let me know if you have any further trouble!
First thanks for this wonderful doublestar glob, it makes file matching very easy.
A possible bug we encountered in our usage of doublestar.Glob:
When a file has its name starting with "【" ( Lenticular bracket wikipedia , ulookup ) it doesnt seem to match. Having the "【" in the path or in the filename but not as first character the file matches.
An example to illustrate the issue.
note: the second file has the filename starting with "【" while the third has an extra space added " 【" ( can be any
normal
char instead of space )Running the below code ( close to our use case)
The files printed ( matched ) are the first and the last not the second.
Apart from "【" i would suspect more special unicode characters won't match.
The text was updated successfully, but these errors were encountered: