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 vinay.sajip
Recipients alanr, erlendaasland, jaraco, ned.deily, ronaldoussoren, vinay.sajip, youtux
Date 2021-01-06.17:30:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1609954215.84.0.324277608336.issue38780@roundup.psfhosted.org>
In-reply-to
Content
TBH as I said in the now-closed PR, using a NullSocket seems overkill. As mentioned in msg359594, it seems to make more sense to assign a socket attribute to None early in the constructor. If an error occurs during socket creation, the socket attribute will remain at None. When closing, just ensure the socket attribute isn't None before trying to close it. This mirrors what SocketHandler does.
History
Date User Action Args
2021-01-06 17:30:15vinay.sajipsetrecipients: + vinay.sajip, ronaldoussoren, jaraco, ned.deily, youtux, erlendaasland, alanr
2021-01-06 17:30:15vinay.sajipsetmessageid: <1609954215.84.0.324277608336.issue38780@roundup.psfhosted.org>
2021-01-06 17:30:15vinay.sajiplinkissue38780 messages
2021-01-06 17:30:15vinay.sajipcreate