On Thu, 16 Sep 2010 15:51:38 +1000, James Mills wrote:
> On Thu, Sep 16, 2010 at 2:49 PM, Ned Deily wrote:
>> If the problem is that the socket object in question no longer exists,
>> you can protect your code there by enclosing the remove operation in a
>> try block, like:
>
>
> The question t
> Please show the *exact* error message, including the traceback, by
> copying and pasting it. Do not retype it by hand, or summarize it, or put
> it into your own words.
Unfortunately this is not possible. The logging system I designed only
gives the following information, as we have millions of
On Thu, Sep 16, 2010 at 2:49 PM, Ned Deily wrote:
> If the problem is that the socket object in question no longer exists,
> you can protect your code there by enclosing the remove operation in a
> try block, like:
The question that remains to be seen however is:
Why does your list contain dirt
On Wed, 15 Sep 2010 21:05:49 -0700, k3xji wrote:
> Hi all,
>
> We have a select-based server written in Python. Occasionally, maybe
> twice a month there occurs a weird problem, select() returns with
> filedescriptor out of range in select() error. This is of course a
> normal error and handled g
In article
,
k3xji wrote:
> We have a select-based server written in Python. Occasionally, maybe
> twice a month there occurs a weird problem, select() returns with
> filedescriptor out of range in select() error. This is of course a
> normal error and handled gracefully. Our policy is to take d
Hi all,
We have a select-based server written in Python. Occasionally, maybe
twice a month there occurs a weird problem, select() returns with
filedescriptor out of range in select() error. This is of course a
normal error and handled gracefully. Our policy is to take down few
users for select() t
