Jason R. Coombs <jar...@jaraco.com> added the comment:
I've released zipp 3.2.0 that includes a fix for this issue (option 2). Please test it out. Because this change affects the user's expectation about the effect of what's passed in, I'm hesitant to backport it to 3.8 and 3.9. It's too late to go into 3.9.0, so the earliest it can appear is in 3.9.1. Please advise - does the undesirable behavior warrant a bugfix backport, or is it sufficient to direct users impacted by this issue prior to Python 3.10 to use the `zipp` backport? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue40564> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
