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 pitrou
Recipients alex, amaury.forgeotdarc, benjamin.peterson, brian.curtin, exarkun, pitrou
Date 2010-10-14.09:03:23
SpamBayes Score 0.0196823
Marked as misclassified No
Message-id <>
There is a slight issue with warnings, and that's the filtering by module/location. Since these warnings will occur in destructors, they can appear at any point without being related to the code being executed. The "default" filtering method (print the first occurrence of matching warnings for each location where the warning is issued) then is not appropriate; therefore I suggest a separate warning category (ResourceWarning?) for which people can enable different rules.
Date User Action Args
2010-10-14 09:03:25pitrousetrecipients: + pitrou, exarkun, amaury.forgeotdarc, benjamin.peterson, alex, brian.curtin
2010-10-14 09:03:24pitrousetmessageid: <>
2010-10-14 09:03:23pitroulinkissue10093 messages
2010-10-14 09:03:23pitroucreate