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, maker, pitrou, r.david.murray, terry.reedy, vinay.sajip
Date 2012-05-15.21:15:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> If you get a warning, it means your tests lack proper cleanup, so you
> should fix that instead of trying to make the warning disappear by
> circumventing regrtest's detection mechanism.

What makes you say I was trying to circumvent regrtest's detection mechanism? I wasn't. Isn't it the case that tests shouldn't affect global state? Since regrtest told me that global state was being changed by the smtpd module used by the test, I tried to find a way of avoiding changing global state in my test - but because of the problem I mention, I couldn't see a way of using smtpd without affecting global state. This is partly because of an underlying wart in asyncore, which this issue is trying to address.

Do you have a proposal about how to solve this - is there something you think I've missed? Do you have specific concerns about the approach being discussed?
Date User Action Args
2012-05-15 21:15:14vinay.sajipsetrecipients: + vinay.sajip, terry.reedy, pitrou, giampaolo.rodola, r.david.murray, maker
2012-05-15 21:15:14vinay.sajipsetmessageid: <>
2012-05-15 21:15:13vinay.sajiplinkissue11959 messages
2012-05-15 21:15:13vinay.sajipcreate