![](https://secure.gravatar.com/avatar/7433ccc4d72b41e859d7c3740b8cb178.jpg?s=120&d=mm&r=g)
----- Original Message ----- From: <glyph@divmod.com> To: "Twisted general discussion" <twisted-python@twistedmatrix.com> Sent: Saturday, December 31, 2005 4:33 PM Subject: Re: [Twisted-Python] Re: plus mode was Re: how winnt fileops workand what to do about it
On Sat, 31 Dec 2005 15:21:45 -0500, Paul G <paul-lists@perforge.com> wrote:
2. say that across all platforms python supports given functionality on, said functionality needs to have functionally identical results given identical input. in this case, the flush+seek workaround needs to be utilized on all cpythons linked with msvscrt in a manner transparent to the user.
It seems like we can work around this more easily than that, considering that flush and seek are available from Twisted; the file object causing problems in the tests is being returned from the open() method of a FilePath object, if I understand it correctly. FilePath could include the workaround far in advance of Python deciding to.
oh, it makes perfect sense to have a workaround in twisted, i'm not suggesting otherwise. however, it should be just that - a temporary workaround until cpython has a fix for the issue, because (outside of the offending libc implementation), that is the right place to fix it. -p