Message155023
| Author |
Mark.Shannon |
| Recipients |
Jim.Jewett, Mark.Shannon, gvanrossum, python-dev, rhettinger, vstinner |
| Date |
2012年03月06日.16:56:28 |
| SpamBayes Score |
9.4759756e-12 |
| Marked as misclassified |
No |
| Message-id |
<4F5641BE.40301@hotpy.org> |
| In-reply-to |
<1331051737.81.0.0806691062949.issue14205@psf.upfronthosting.co.za> |
| Content |
Jim Jewett wrote:
> Jim Jewett <jimjjewett@gmail.com> added the comment:
>
> Can't this be triggered by non-malicious code that just happened to have a python comparison and get hit with a thread switch?
So, they are writing to a dict in one thread while reading from the same
dict in another thread, without any external locks and with keys written
in Python.
>
> I'm not sure how often it happens, but today it would not be visible to the user; after the patch, users will see a sporadic failure that they can't easily defend against.
>
I suspect, they are already seeing sporadic failures.
I think raising an exception is better than weird failures.
We should document the new behaviour, as it is a change in semantics. |
|