RetroSearch Browse

Sat Mar 31 19:03:13 CEST 2012 · https://mail.python.org/pipermail/python-dev/2012-March/118362.html

On Sun, Apr 1, 2012 at 2:09 AM, Guido van Rossum <guido at python.org> wrote:
> Here's a different puzzle. Has anyone written a demo yet that provokes
> this RuntimeError, without cheating? (Cheating would be to mutate the
> dict from *inside* the __eq__ or __hash__ method.) If you're serious
> about revisiting this, I'd like to see at least one example of a
> program that is broken by the change. Otherwise I think the status quo
> in the 3.3 repo should prevail -- I don't want to be stymied by
> superstition.

I attached an attempt to *deliberately* break the new behaviour to the
tracker issue. It isn't actually breaking for me, so I'd like other
folks to look at it to see if I missed something in my implementation,
of if it's just genuinely that hard to induce the necessary bad timing
of a preemptive thread switch.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2012-March/118362.html below:

[Python-Dev] Issue 14417: consequences of new dict runtime error