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 christian.heimes
Recipients asvetlov, brandon-rhodes, christian.heimes, dstufft, giampaolo.rodola, jcea, jgehrcke, kristjan.jonsson, martius, njs, orsenthil, pitrou
Date 2017-12-01.09:25:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Correct, PEP 543 won't land in Python 3.7 because neither me nor Cory have the resources to land it. However I want all changes and new additions to the SSL module to follow PEP 543 so I can provide a PEP 543-compatible interface in the near future (3.8 or 3.9). We need a proper certificate class anyway to address other issues and feature requests. I don't want to have three ways to load certificates, especially when it involves more C code.
Date User Action Args
2017-12-01 09:25:34christian.heimessetrecipients: + christian.heimes, jcea, orsenthil, pitrou, kristjan.jonsson, giampaolo.rodola, njs, asvetlov, jgehrcke, brandon-rhodes, dstufft, martius
2017-12-01 09:25:34christian.heimessetmessageid: <>
2017-12-01 09:25:34christian.heimeslinkissue16487 messages
2017-12-01 09:25:34christian.heimescreate