Repository navigation
Conversation
…ng matches + Performance not seem to be affected when measure with cygwin-python-2.
|
Looks good, thanks for the patch. |
…gurable norm/case-sensitive/slashes preserving matches"
|
The LRU bug was introduced here :( 6876675#diff-b702bab9f1fd8e250b7d429a75486ba2L38 |
|
By the way, to really fix case-conversion of matches(#10), the defaults must change to: |
|
You mean there is something else to be done here? Actually, looking at it more, I think we broke backwards compatibility here. The behaviour changed from not caring about case-sensitivity, to caring about it by default. Am I wrong? |
|
This PR preserves the behavior of the library, but library's behavior so far did not preserve the case of matches. So I said that in order to imitate Python's behavior, you need to set the defaults I described above in the various keyword-arguments. Does that make sense? |
Yes. and a note that if the program runs also in POSIX, adding |
FIX #10 to be possible to preserve the matched captures.
Previously all matches were passed through
os.path.normcase(), which in Windows, it converts them to lower-cases.The resulting matches would then break user-code when it runs on POSIX and non-POSIX systems (e.g. running a Makefile-like python tool).
Note that python stdlib does not by default pass al filepaths through
normcase()- this is left to the discretion of the user.