On Thu, 16 Sep 2010 15:51:38 +1000, James Mills wrote: > On Thu, Sep 16, 2010 at 2:49 PM, Ned Deily <n...@acm.org> 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 dirty data ? Your code has likely removed the > socket object from the list before, why is it attempting to remove it > again ? > > I would consider you re-look at your code's logic rather than patch up > the code with a "band-aid-solution".
Well said. -- Steven -- http://mail.python.org/mailman/listinfo/python-list
