[issue3806] LockTests in test_imp should be skipped when thread is not available

Changes by Hirokazu Yamamoto <[EMAIL PROTECTED]>: -- resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue3806] LockTests in test_imp should be skipped when thread is not available

Hirokazu Yamamoto <[EMAIL PROTECTED]> added the comment: Thanks. Fixed in r66319(trunk) and r66334(py3k). ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3806] LockTests in test_imp should be skipped when thread is not available

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: Looks good to me. ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list mailin

[issue3806] LockTests in test_imp should be skipped when thread is not available

Hirokazu Yamamoto <[EMAIL PROTECTED]> added the comment: Like attached new patch? There was no strong meaning. :-) del tests[0] can can preserve order of tests, but it's not so important, is it. Added file: http://bugs.python.org/file11428/test_imp.patch ___

[issue3806] LockTests in test_imp should be skipped when thread is not available

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: Why not just append LockTests to the tests after instead of deleting it from the list? -- nosy: +benjamin.peterson ___ Python tracker <[EMAIL PROTECTED]> _

[issue3806] LockTests in test_imp should be skipped when thread is not available

New submission from Hirokazu Yamamoto <[EMAIL PROTECTED]>: LockTests is meaningfull only when thread is available, so this patch removes it from tests when thread is unavailable. This patch is for trunk. -- components: Tests files: test_imp.patch keywords: patch messages: 72801 nosy: oce