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 vstinner
Recipients vstinner
Date 2017-08-18.17:12:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1503076378.29.0.950087882836.issue31234@psf.upfronthosting.co.za>
In-reply-to
Content
Currently, support.threading_cleanup() waits 1 second before emitting a warning about threads running in the background. I propose to emit immediately the warning to be able to catch bugs quicker, bugs like bpo-31233 or bpo-30830.

The problem is that currently, 12 test files still leak threads:
---
12 tests altered the execution environment:
    test_asyncio test_concurrent_futures test_fork1 test_httpservers
    test_logging test_pydoc test_ssl test_thread test_threaded_import
    test_threading test_wait3 test_xmlrpc
---

Since threading_cleanup() warnings now mark tests as failed, we should first fix these tests before being able to make support.threading_cleanup() stricter.
History
Date User Action Args
2017-08-18 17:12:58vstinnersetrecipients: + vstinner
2017-08-18 17:12:58vstinnersetmessageid: <1503076378.29.0.950087882836.issue31234@psf.upfronthosting.co.za>
2017-08-18 17:12:58vstinnerlinkissue31234 messages
2017-08-18 17:12:58vstinnercreate