>>> "Jason R. Mastaler" wrote > There's a workaround, but the problem is that I think I'll be the one > bearing the brunt of this bug for who knows how long. I've gotten > about a half dozen problem reports about it already on the TMDA lists. > TMDA uses os.fsync() in its mbox and Maildir delivery code, so > practically every user will find their TMDA broken as soon as they > install or upgrade to 2.3.1. Since Python point releases are usually > so solid, they don't consider it might be a bug in the interpreter, > and assume it's a TMDA bug. TMDA is just one example. Repeat for the > other packages out there which rely on os.fsync(). Hm. I ran the Zope2, Zope3, and Twisted test suites against the release build before the release. I'm open to additional suggestions (I just grabbed tmda, but it doesn't have a test suite). In this case, the problem hopefully would've been picked up with a release candidate, but I'm also happy to add additional slabs of test suites to run against code before it's released... Anthony -- Anthony Baxter <anthony at interlink.com.au> It's never too late to have a happy childhood.
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