R. David Murray <rdmur...@bitdance.com> added the comment: The traceback I posted was a spurious result of my misunderstanding your test code. With -uall it worked fine. Sorry that I didn't make that clear.
Thanks for doing the work of putting the extended test framework together. Without that, this would probably have remained stuck. I don't think the test_socketserver code is a particularly good example of unittest code, though, so I refactored what you did into something I like better. I may be wrong, so feedback welcome. Alternative test_imaplib patch attached. Note that in looking at this I discovered that the test suite as a whole does not currently handle --without-threads cleanly. I've opened issue 7449 for this. Since test_imaplib currently only has one non-thread-dependent test, I've written my version of the patch so that the whole test is skipped if threading is not available (this skip will come with an appropriate message in the test output). Note also that my code generates a traceback analogous to the one I posted but only when run under -R. I'll have to look in to that. ---------- assignee: -> r.david.murray _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue5949> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
