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 Arfrever, barry, benjamin.peterson, eric.snow, hodgestar, pitrou, python-dev, rhettinger, robagar, serhiy.storchaka
Date 2017-09-12.11:05:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
What the problem tries to solve PR 3508? Swallowing all exceptions looks like an antipattern to me. This puts the problem under the carpet. Rather than failing and allowing the programmer to fix the picleability of its class, this can silently produce incorrect pickle data. By swallowing MemoryError and RecursionError this changes the behavior of objects in an environment with limited resources: lack of memory or calling deep in the calling stack. This adds heisenbugs. An infinity recursion spends CPU time, and in unlucky cases can cause a crash. It is better to detect it earlier than just swallow RecursionError.
Date User Action Args
2017-09-12 11:05:00serhiy.storchakasetrecipients: + serhiy.storchaka, barry, rhettinger, pitrou, benjamin.peterson, hodgestar, Arfrever, python-dev, eric.snow, robagar
2017-09-12 11:05:00serhiy.storchakasetmessageid: <>
2017-09-12 11:05:00serhiy.storchakalinkissue16251 messages
2017-09-12 11:05:00serhiy.storchakacreate