"Jason R. Mastaler" wrote martin@v.loewis.de (Martin v. Löwis) writes:
I don't think the problem is severe; os.fsync is rarely used.
How did you arrive at this notion?
Hm. The only usage of it I can find in the Zope2, Zope3 and Twisted codebases is a single use inside zodb, and it's wrapped in a check that os.fsync exists (since it's not available on all platforms). I also did a grep over all the python packages I've downloaded or installed (which is a _lot_) and the TMDA code is the only package to use it. I'm still planning on cutting a 2.3.2 to fix the problem, but I see no reason to make any further steps to "revoke" 2.3.1 further than the warning message on the release page - which is mostly aimed at people who might be planning to package the code. Anthony -- Anthony Baxter <anthony@interlink.com.au> It's never too late to have a happy childhood.