➜

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 brett.cannon
Recipients alex, amaury.forgeotdarc, benjamin.peterson, brett.cannon, brian.curtin, exarkun, giampaolo.rodola, pitrou
Date 2010-10-22.20:01:12
SpamBayes Score 0.0016714049
Marked as misclassified No
Message-id <AANLkTinBMU4mXdEDSRjQ-zHoTt1o-wEXAZCwSPR0M5H7@mail.gmail.com>
In-reply-to <1287776997.87.0.743075126003.issue10093@psf.upfronthosting.co.za>
Content 
On Fri, Oct 22, 2010 at 12:49, Antoine Pitrou <report@bugs.python.org> wrote:
>
> Antoine Pitrou <pitrou@free.fr> added the comment:
>
>> After thinking about what warning to go with, I take back my python-dev
>> suggestion of ResourceWarning and switch to DebugWarning.
>
> So what is your advice now?
> I've thought about the DebugWarning name myself and I think it's a rather bad name, because many warnings are debug-related in practice. I'd just say stick with ResourceWarning.

That's true. And the warning hierarchy is rather shallow anyway. I'm
fine with ResourceWarning then.
History
Date User Action Args
2010-10-22 20:01:14brett.cannonsetrecipients: + brett.cannon, exarkun, amaury.forgeotdarc, pitrou, giampaolo.rodola, benjamin.peterson, alex, brian.curtin
2010-10-22 20:01:12brett.cannonlinkissue10093 messages
2010-10-22 20:01:12brett.cannoncreate