Message 270609 - 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.

In-reply-to
Author	Александр Карпинский
Recipients	serhiy.storchaka, Александр Карпинский
Date	2016年07月17日.05:46:23
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1468734384.13.0.305671408266.issue27535@psf.upfronthosting.co.za>

Content
@serhiy.storchaka Any filters not solves the problem because warnings module SAVES EVERY WARNING MESSAGE for further duplication checks. Yes, the file name is helpful for determining the source of the POSSIBLE leak. While file name in error message IS SOURCE OF THE LEAK. When you aware about not closed files, you can log file names. You have a way to do that. But if you want to ignore the warning, the memory will leak. Not because of not closed files, but because of warning itself. I do want to close files in my script, but in Pillow, it is not so easy due to backward compatibility.

Content

@serhiy.storchaka
Any filters not solves the problem because warnings module SAVES EVERY WARNING MESSAGE for further duplication checks.
Yes, the file name is helpful for determining the source of the POSSIBLE leak. While file name in error message IS SOURCE OF THE LEAK. When you aware about not closed files, you can log file names. You have a way to do that. But if you want to ignore the warning, the memory will leak. Not because of not closed files, but because of warning itself.
I do want to close files in my script, but in Pillow, it is not so easy due to backward compatibility.

History
Date	User	Action	Args
2016年07月17日 05:46:24	Александр Карпинский	set	recipients: + Александр Карпинский, serhiy.storchaka
2016年07月17日 05:46:24	Александр Карпинский	set	messageid: <1468734384.13.0.305671408266.issue27535@psf.upfronthosting.co.za>
2016年07月17日 05:46:24	Александр Карпинский	link	issue27535 messages
2016年07月17日 05:46:23	Александр Карпинский	create

homepage