Re: EINTR ... was Re: [Zope-dev] browser closing connection

2001-12-11 Thread Jeremy Hylton
MTK == Matthew T Kromer [EMAIL PROTECTED] writes: MTK For what its worth, I tracked this down in the sources and MTK confirmed that in Zope 2.3, we shipped a modified asyncore.py MTK with Medusa that handled EINTR, but in Zope 2.4 we used stock MTK Python's asyncore which does NOT

Re: EINTR ... was Re: [Zope-dev] browser closing connection

2001-12-11 Thread Leonardo Rochael Almeida
So, which is the official way of fixing Zope 2.4.3? wait for a hotfix? apply Matthew's patch? steal asyncore from Python 2.2? On Tue, 2001-12-11 at 12:52, Jeremy Hylton wrote: MTK == Matthew T Kromer [EMAIL PROTECTED] writes: MTK For what its worth, I tracked this down in the sources and

Re: EINTR ... was Re: [Zope-dev] browser closing connection

2001-12-11 Thread John Ziniti
Replace your Python 2.1.1 asyncore.py with the one that is attached. I've been using it for months now with no problems. Notice, however, that it doesn't work on WinNT, b/c the author didn't know what EINTR looked like on NT Leonardo Rochael Almeida wrote: So, which is the official way of

Re: EINTR ... was Re: [Zope-dev] browser closing connection

2001-12-11 Thread Jeremy Hylton
JZ == John Ziniti [EMAIL PROTECTED] writes: JZ Replace your Python 2.1.1 asyncore.py with the one that is JZ attached. I've been using it for months now with no problems. JZ Notice, however, that it doesn't work on WinNT, b/c the author JZ didn't know what EINTR looked like on NT The