Jason R. Coombs <jar...@jaraco.com> added the comment:
Thanks sorrow for filing a report. I primarily developed this functionality. As I did, I found the 'zip' format to be under-specified, so I used real-world examples as models to infer a spec. It seems you may have discovered a use-case that violates that expectation, a case where `/a.txt` is identical to `a.txt`. My instinct is that `zipfile.Path` should support 99% of real-world use-cases and that other use-cases may not be supported or may require additional consideration (wrappers, subclasses) to support. Can you tell me more about your use-case and why zipp.Path/zipfile.Path should support it? Is this behavior a result of a real-world example (please share details about the origin) or contrived? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue41035> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
