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 gvanrossum
Recipients Arfrever, Jim.Jewett, asvetlov, gregory.p.smith, gvanrossum, ncoghlan, pitrou, r.david.murray, rhettinger, skrah, vstinner
Date 2012-04-05.16:50:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAP7+vJJLRTEBM30KNAUsPUwzxaWAT7ubqm+14pGNN2o9nYth_w@mail.gmail.com>
In-reply-to <1333625102.98.0.249770296229.issue14417@psf.upfronthosting.co.za>
Content
> A counter can be added to dictobject.c.patch to avoid an infinite loop.

But why bother? There was no counter originally -- it would continue
until it ran out of stack. Since this can only be triggered if there
is Python code in the __eq__, that means that it is still
interruptable with ^C.

Does this mean I should just check it in? But I asked, and never got
an answer, whether the original stress test had been converted into a
unittest. I'd like that to happen before I check this in. Also there
are probably docs I've missed. Somebody please help!
History
Date User Action Args
2012-04-05 16:50:07gvanrossumsetrecipients: + gvanrossum, rhettinger, gregory.p.smith, ncoghlan, pitrou, vstinner, Arfrever, r.david.murray, asvetlov, skrah, Jim.Jewett
2012-04-05 16:50:06gvanrossumlinkissue14417 messages
2012-04-05 16:50:06gvanrossumcreate