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 serhiy.storchaka
Recipients Antony.Lee, Jim.Jewett, Trundle, Yury.Selivanov, alex, barry, benjamin.peterson, berker.peksag, cvrebert, daniel.urban, eric.araujo, fijal, gcbirzan, georg.brandl, gvanrossum, jamesh, josh.r, jwilk, martin.panter, ncoghlan, pitrou, r.david.murray, serhiy.storchaka, yorik.sar
Date 2018-04-13.19:09:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Silencing exceptions like MemoryError, RecursionError or KeyboardInterrupt and returning a lying result doesn't look like a good idea to me. These exceptions can be raised in virtually any code for causes not related to executed code. MemoryError -- if other parts of the program allocated too much memory, RecursionError -- if the exception check is performed too deep in the execution stack, KeyboardInterrupt -- for obvious reasons.
Date User Action Args
2018-04-13 19:09:29serhiy.storchakasetrecipients: + serhiy.storchaka, gvanrossum, barry, georg.brandl, jamesh, ncoghlan, pitrou, fijal, benjamin.peterson, jwilk, eric.araujo, alex, r.david.murray, Trundle, cvrebert, daniel.urban, yorik.sar, Yury.Selivanov, berker.peksag, martin.panter, Jim.Jewett, gcbirzan, Antony.Lee, josh.r
2018-04-13 19:09:29serhiy.storchakasetmessageid: <>
2018-04-13 19:09:29serhiy.storchakalinkissue12029 messages
2018-04-13 19:09:29serhiy.storchakacreate