> so, still: sorry no, the application should not just look at the result > being returned. If it doesn't want to lose data, it *has* to, because of the way it's currently implemented. There is no other way (other than ignoring the error) in Python 2.5.x and earlier. > The mmap.flush method should be fixed. I never debated that. I debated whether that is a "rather severe" issue, which I still don't think it is. Regards, Martin
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