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 r.david.murray
Recipients gvanrossum, r.david.murray, vstinner, yselivanov
Date 2014-10-07.01:08:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1412644088.59.0.902099699208.issue22572@psf.upfronthosting.co.za>
In-reply-to
Content
The 'Server did not stop' error was lying in wait for the NoneType bug to be fixed :)  So, if you didn't the NoneType, my test case isn't reproducing the problem for you, which is odd.  Using call_soon_threadsafe from an addCleanup in the _server method makes it work for me.  (Seems to work even without the threadsafe, but I think I'll keep it!)  Perhaps seeing the NoneType error is a timing issue, given that the problem is thread safety.

So, my apologies for the noise.  I guess I'm too used to threads, where it is typical to call the close or stop method from another thread.
History
Date User Action Args
2014-10-07 01:08:08r.david.murraysetrecipients: + r.david.murray, gvanrossum, vstinner, yselivanov
2014-10-07 01:08:08r.david.murraysetmessageid: <1412644088.59.0.902099699208.issue22572@psf.upfronthosting.co.za>
2014-10-07 01:08:08r.david.murraylinkissue22572 messages
2014-10-07 01:08:07r.david.murraycreate