[Greg Ewing] > If that's the only problem, then surely it's just a matter of correct > GIL usage? I.e. if a thread using a file object releases the GIL, it > should re-acquire it and check that the FILE * in the file object is > still valid before using it again. Greg, read the patch comments -- they've been there a long time. There would be no problem if Python didn't release the GIL around potentially blocking I/O calls. But the instant you release the GIL, you have no guarantee that f->f_fp won't change to NULL from one nanosecond to the next. There isn't a simple solution to this.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4