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 jbfzs, r.david.murray, rhettinger, serhiy.storchaka, vstinner, Александр Карпинский
Date 2017-11-21.14:46:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1511275571.33.0.213398074469.issue27535@psf.upfronthosting.co.za>
In-reply-to
Content
The problem is not the function displaying the warning, but warnings registries (__warningregistry__) no?

The behaviour depends on the action of the filter matching the ResourceWarning warning:

* always: don't touch the registry => no leak
* ignore: add the key to registry => leak!
* another action: add the key to registry => leak!

The key is the tuple (text, category, lineno).

I understand why always doesn't touch the registry. But why does "ignore" action touch the registry? Not only the user will not see the message, but the memory will slowly grow in the background.
History
Date User Action Args
2017-11-21 14:46:11vstinnersetrecipients: + vstinner, rhettinger, r.david.murray, serhiy.storchaka, Александр Карпинский, jbfzs
2017-11-21 14:46:11vstinnersetmessageid: <1511275571.33.0.213398074469.issue27535@psf.upfronthosting.co.za>
2017-11-21 14:46:11vstinnerlinkissue27535 messages
2017-11-21 14:46:11vstinnercreate