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 belopolsky
Recipients ajaksu2, alexandre.vassalotti, belopolsky, ddorfman, rhettinger
Date 2010-07-20.05:38:28
SpamBayes Score 0.00509264
Marked as misclassified No
Message-id <>
As I explained in msg110617 under issue9269, it is possible that we can do better than simply detect reduce cycles and bail out.

I am torn between two options:

1. Reject this patch and wait until a proper solution is found.

2. Admit that better is the enemy of good and start with proper error reporting on reduce cycles by accepting this patch.

My only concern about this patch is that it is likely to affect performance because pickling will have to maintain the "reducing_now" dictionary that is parallel to the memo dictionary.
Date User Action Args
2010-07-20 05:38:32belopolskysetrecipients: + belopolsky, rhettinger, ddorfman, ajaksu2, alexandre.vassalotti
2010-07-20 05:38:32belopolskysetmessageid: <>
2010-07-20 05:38:29belopolskylinkissue1062277 messages
2010-07-20 05:38:28belopolskycreate