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 lemburg
Recipients alex, amaury.forgeotdarc, benjamin.peterson, brett.cannon, brian.curtin, exarkun, giampaolo.rodola, lemburg, pitrou
Date 2010-10-29.13:25:58
SpamBayes Score 2.52528e-07
Marked as misclassified No
Message-id <>
In-reply-to <1288357616.3565.76.camel@localhost.localdomain>
Antoine Pitrou wrote:
> Antoine Pitrou <> added the comment:
>> The warning will trigger without any reason.
> Well, by now you should have understood the reason, so I conclude that
> you are either 1) deaf 2) stupid 3) deliberately obnoxious.
> This is my last answer to you on this topic. Goodbye.

Ignoring your insults, I think the problem is that you fail to see
point or address it:

Warnings in Python are meant to tell programmers that something
should be fixed. The warnings in the examples I gave do not point
to cases that need to be fixed, in fact, they are very common
idioms used in Python books, examples and tutorials.

Note that you've just added warning filters to the test suite
to ignore the warning again. I find that a good argument
for not having it in this form in the first place.

A truely useful ResourceWarning would trigger if resources gets
close to some limit, e.g. if the number of open file descriptors
reaches a certain limit. This could easily be tested when
opening them, since they are plain integers.
Date User Action Args
2010-10-29 13:26:02lemburgsetrecipients: + lemburg, brett.cannon, exarkun, amaury.forgeotdarc, pitrou, giampaolo.rodola, benjamin.peterson, alex, brian.curtin
2010-10-29 13:25:59lemburglinkissue10093 messages
2010-10-29 13:25:58lemburgcreate