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 giampaolo.rodola, r.david.murray, terry.reedy, vinay.sajip
Date 2011-05-10.15:11:11
SpamBayes Score 4.572748e-09
Marked as misclassified No
Message-id <>
The overridden create_socket() method will have the same behaviour for the case when a socket map is *not* passed in to smtpd.__init__(). Users using the existing signature for the constructor will cause the sockmap instance attribute to be set to None, and this will get passed in to set_socket just as was happening before. So the only time the overridden create_socket will behave differently is if a non-None value is passed into smtpd.__init__(), and that's by design.

Of course there is a slightly increased maintenance burden, in that other functional changes to asyncore.dispatcher.create_socket will need to be duplicated in smtpd.create_socket. However, such changes would be fairly infrequent, methinks. A comment could be added to asyncore.dispatcher.create_socket if necessary, to remind maintainers about this.
Date User Action Args
2011-05-10 15:11:21vinay.sajipsetrecipients: + vinay.sajip, terry.reedy, giampaolo.rodola, r.david.murray
2011-05-10 15:11:21vinay.sajipsetmessageid: <>
2011-05-10 15:11:11vinay.sajiplinkissue11959 messages
2011-05-10 15:11:11vinay.sajipcreate