Message 220804 - Python tracker

➜

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	benjamin.peterson, vstinner
Date	2014-06-17.07:40:26
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1402990827.19.0.536092854004.issue21788@psf.upfronthosting.co.za>
In-reply-to

Content
Hi, During the development of Python 3.4, I tried to emit warnings if a file is destroyed without being explicitly closed. The warnings were not emited in threads during Python finalization. Here are related changes: - Issue #19421: "FileIO destructor imports indirectly the io module at exit" - Issue #19424: "_warnings: patch to avoid conversions from/to UTF-8" - Issue #19442: "Python crashes when a warning is emitted during shutdown" - Change in Python shutdown: issue #19466 "Clear state of threads earlier in Python shutdown" - Regression => issue #20526 The change #19466 had to be reverted a few days before the release of Python 3.4.0 because it caused the regression #20526. I'm still not convinced that #20526 was a new bug. IMO the bug still exists, but it is just less likely without the change #19466. There is still something wrong in Python finalization, so I open this issue to rework it. The goal is to get warnings in test_4_daemon_threads() of test_threading. I attached the test as a Python script.

Hi,

During the development of Python 3.4, I tried to emit warnings if a file is destroyed without being explicitly closed. The warnings were not emited in threads during Python finalization. Here are related changes:

- Issue #19421: "FileIO destructor imports indirectly the io module at exit"
- Issue #19424: "_warnings: patch to avoid conversions from/to UTF-8"
- Issue #19442: "Python crashes when a warning is emitted during shutdown"
- Change in Python shutdown: issue #19466 "Clear state of threads earlier in Python shutdown"
- Regression => issue #20526

The change #19466 had to be reverted a few days before the release of Python 3.4.0 because it caused the regression #20526.

I'm still not convinced that #20526 was a new bug. IMO the bug still exists, but it is just less likely without the change #19466.

There is still something wrong in Python finalization, so I open this issue to rework it.

The goal is to get warnings in test_4_daemon_threads() of test_threading. I attached the test as a Python script.

History
Date	User	Action	Args
2014-06-17 07:40:27	vstinner	set	recipients: + vstinner, benjamin.peterson
2014-06-17 07:40:27	vstinner	set	messageid: <1402990827.19.0.536092854004.issue21788@psf.upfronthosting.co.za>
2014-06-17 07:40:27	vstinner	link	issue21788 messages
2014-06-17 07:40:26	vstinner	create