This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author jaraco
Recipients bustawin, jaraco, xtreak
Date 2020-09-23.13:29:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
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?
Date User Action Args
2020-09-23 13:29:58jaracosetrecipients: + jaraco, xtreak, bustawin
2020-09-23 13:29:58jaracosetmessageid: <>
2020-09-23 13:29:58jaracolinkissue40564 messages
2020-09-23 13:29:58jaracocreate