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 Ron Frederick
Recipients Ron Frederick, asvetlov, gvanrossum, vstinner, yselivanov
Date 2017-12-21.02:54:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1513824860.7.0.213398074469.issue25749@psf.upfronthosting.co.za>
In-reply-to
Content
In my original report, I suggested _either_ exporting asyncio.Server since that's what was documented elsewhere _OR_ adding AbstractServer to the documentation and changing existing references to asyncio.Server to point at asyncio.AbstractServer instead, as that symbol is already exported but is not currently documented. There appear to be good reasons for hiding the implementation details of Server, and I'm good with that. I just think the docs and the exports need to agree on one or the other.

I originally had references to AbstractServer in my project docs, but changed them to Server after seeing that only Server was currently in the public Python documentation.

As for references to the "sockets" member of Server, I'm not currently relying on that in my code. I have code that can handle getaddrinfo() returning more than one address to listen on, but I create separate Server instances for each individual address right now, as this gives me better control when a caller asks to listen on a dynamic port on multiple interfaces at once.
History
Date User Action Args
2017-12-21 02:54:20Ron Fredericksetrecipients: + Ron Frederick, gvanrossum, vstinner, asvetlov, yselivanov
2017-12-21 02:54:20Ron Fredericksetmessageid: <1513824860.7.0.213398074469.issue25749@psf.upfronthosting.co.za>
2017-12-21 02:54:20Ron Fredericklinkissue25749 messages
2017-12-21 02:54:19Ron Frederickcreate