Tim> http://www.python.org/sf/595601
Tim> has been in limbo a long time. Looks like it popped up in real
Tim> life, in Zope last week.
Tim> Quickie: if you let run this long enough, it will die with a
Tim> segfault (and under any version of Python):
...
Isn't this a case of "so don't do that"? I've never encountered this
before, but then I don't close files in one thread while another holds a
reference.
Would it be reasonable to raise an error or warning if a file's close()
method was called when the reference count was greater than 1?
Skip
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