Message278934
| Author |
vstinner |
| Recipients |
christian.heimes, methane, ned.deily, serhiy.storchaka, vstinner, yselivanov |
| Date |
2016年10月18日.20:03:23 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<CAMpsgwbv=EVm-PL+QZXynt=CoS=NHy5SDZ=NgSO360KPSF0Xaw@mail.gmail.com> |
| In-reply-to |
<1476818785.94.0.307514380555.issue28471@psf.upfronthosting.co.za> |
| Content |
> Fatal Python error: Python memory allocator called without holding the GIL
Oh, I didn't expect that my new check would catch such bug. Nice.
In release mode, the check is disabled by default (can be enabled at
runtime), and I don't think that the code can crash.
But the bug should be fixed anyway :-) |
|