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 ned.deily
Recipients berker.peksag, brett.cannon, ethan.furman, jtf621, ned.deily, r.david.murray, serhiy.storchaka, steve.dower
Date 2017-02-28.04:15:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> Note that Ned gave us a permission to get this into 3.6.1.

I may have although I don't remember specifically discussing zipfile.  In any case, I'm willing to consider it.  I think you can make good arguments for and against.  Yes, it could smell like adding a feature but, on the other add, one of the implicit goals of 3.6.0 was to make Path objects supported across the standard library as much as possible, so the lack of support in zipfile (and a few other similar modules) could be viewed as bug.  Also, as far as I can tell, this should be a totally upwards-compatible change except in the presumably unlikely case something is counting on getting an exception when passing a Path object to zipfile.  I say we invoke "practicality beats purity" for this as long as Serhiy is OK with having it cherry-picked to 3.6 and as long as no other core developer here has a strong objection.
Date User Action Args
2017-02-28 04:15:18ned.deilysetrecipients: + ned.deily, brett.cannon, r.david.murray, ethan.furman, berker.peksag, serhiy.storchaka, steve.dower, jtf621
2017-02-28 04:15:18ned.deilysetmessageid: <>
2017-02-28 04:15:18ned.deilylinkissue28231 messages
2017-02-28 04:15:17ned.deilycreate