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 yselivanov
Recipients gvanrossum, j1m, python-dev, vstinner, yselivanov
Date 2016-08-09.23:43:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1470786208.82.0.80156754286.issue27392@psf.upfronthosting.co.za>
In-reply-to
Content
> WRT boolean for SSL, I think it's very common for clients to verify server certificates, but relatively uncommon for servers to require client certificates.  The impression I have from reading docs and stack overflow posts that the most common use case for the SSL module is connection to HTTPS sites. For this use case, using a default context makes a lot of sense.

> It seems extremely unlikely to me for a server to use a default context.

I think in this case we should just mimic the API of create_server and create_unix_server.

As for restricting socket family type - I think Guido is right.  Although I'd love uvloop to be 100% compatible, I guess we shouldn't add artificial restrictions: if asyncio already supports AF_BLUETOOTH then let's keep it that way.
History
Date User Action Args
2016-08-09 23:43:28yselivanovsetrecipients: + yselivanov, gvanrossum, vstinner, j1m, python-dev
2016-08-09 23:43:28yselivanovsetmessageid: <1470786208.82.0.80156754286.issue27392@psf.upfronthosting.co.za>
2016-08-09 23:43:28yselivanovlinkissue27392 messages
2016-08-09 23:43:28yselivanovcreate