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 cstratak
Recipients asvetlov, cstratak, yselivanov
Date 2018-11-30.15:13:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1543590780.11.0.788709270274.issue35352@psf.upfronthosting.co.za>
In-reply-to
Content
I believe I figured out the issue, at least on the master branch.

While checking the certificates used by asyncio tests within the test_asyncio folder I noticed they were quite outdated when compared to the more recent updated ones with the test/ folder, which take into account the stronger crypto defaults introduced in the latest openssl versions.

And by looking at https://github.com/python/cpython/commit/6d8c1abb003a4cb05f1ddcf0eeddeeeed513cd57#diff-a8e7dbb528601706db0f01d01332bb76 it seems that those certs are just copied from test/ within test_asyncio/. So by copying over the old certs, the tests actually pass.

The immediate workaround would be to just copy over the certs but a better approach would be to just reuse the certs within the test/ folder instead of relying on copying them over to test_asyncio/
History
Date User Action Args
2018-11-30 15:13:00cstrataksetrecipients: + cstratak, asvetlov, yselivanov
2018-11-30 15:13:00cstrataksetmessageid: <1543590780.11.0.788709270274.issue35352@psf.upfronthosting.co.za>
2018-11-30 15:13:00cstrataklinkissue35352 messages
2018-11-30 15:13:00cstratakcreate