[issue2710] error: (10035, 'The socket operation could not complete without blocking')

2011-01-13 Thread Terry J. Reedy
Terry J. Reedy tjre...@udel.edu added the comment: This can be reopened if the problem ever appears in a current issue. -- resolution: - out of date status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2710

[issue2710] error: (10035, 'The socket operation could not complete without blocking')

2010-12-30 Thread Terry J. Reedy
Terry J. Reedy tjre...@udel.edu added the comment: If there is no verification that there is a bug in 2.7/3.1,2, then I think this should be closed. -- nosy: +terry.reedy versions: -Python 2.6 ___ Python tracker rep...@bugs.python.org

[issue2710] error: (10035, 'The socket operation could not complete without blocking')

2009-08-05 Thread Guilherme Polo
Guilherme Polo ggp...@gmail.com added the comment: I just tried writing tests for it, but I don't know idlelib/rpc.py enough yet. You can see this first attempt at: http://svn.python.org/view?view=revrevision=74320 I started trying to test rpc.RPCClient together with run.main but it seemed too

[issue2710] error: (10035, 'The socket operation could not complete without blocking')

2009-08-04 Thread Gabriel Genellina
Gabriel Genellina gagsl-...@yahoo.com.ar added the comment: AFAIK, WSAEWOULDBLOCK means that the socket is in nonblocking mode and the attempted operation could wait indefinitely to complete. But I don't understand how that could happen since a previous select() confirmed the socket is

[issue2710] error: (10035, 'The socket operation could not complete without blocking')

2009-08-04 Thread Guilherme Polo
Guilherme Polo ggp...@gmail.com added the comment: AFAIK, WSAEWOULDBLOCK means that the socket is in nonblocking mode and the attempted operation could wait indefinitely to complete. Rather pessimistic way to see it :) I've always read it as operation cannot be completed without blocking.

[issue2710] error: (10035, 'The socket operation could not complete without blocking')

2009-08-04 Thread Gabriel Genellina
Gabriel Genellina gagsl-...@yahoo.com.ar added the comment: So this patch should fix it. But I cannot fire the bug using the posted example, and there are no test cases for this module yet, so I could not test it. -- keywords: +patch Added file:

[issue2710] error: (10035, 'The socket operation could not complete without blocking')

2009-08-03 Thread Guilherme Polo
Guilherme Polo ggp...@gmail.com added the comment: Hi Don, I don't think this is an issue about idle competing for tkinter resources (or idle and tkinter competing for resources -- the other meaning I got when reading your message). From what I remember this WSAEWOULDBLOCK is just a way for

[issue2710] error: (10035, 'The socket operation could not complete without blocking')

2009-04-26 Thread Daniel Diniz
Daniel Diniz aja...@gmail.com added the comment: Don: any news on this? Do you still get the same error with 2.6? -- nosy: +ajaksu2, gpolo priority: - normal stage: - test needed type: - behavior versions: +Python 2.6, Python 3.0 -Python 2.5 ___

[issue2710] error: (10035, 'The socket operation could not complete without blocking')

2008-05-11 Thread Georg Brandl
Changes by Georg Brandl [EMAIL PROTECTED]: -- components: +IDLE __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2710 __ ___ Python-bugs-list mailing list Unsubscribe:

[issue2710] error: (10035, 'The socket operation could not complete without blocking')

2008-04-28 Thread Don Hanlen
New submission from Don Hanlen [EMAIL PROTECTED]: IDLE internal error in runcode() Traceback (most recent call last): File C:\PYTHON25\lib\idlelib\rpc.py, line 235, in asyncqueue self.putmessage((seq, request)) File C:\PYTHON25\lib\idlelib\rpc.py, line 332, in putmessage n =

[issue2710] error: (10035, 'The socket operation could not complete without blocking')

2008-04-28 Thread Don Hanlen
Don Hanlen [EMAIL PROTECTED] added the comment: ah, lines 284-289 (the lines in question) need indenting 4 levels. I just DL'd 2.5.2, ran the code once, no problem, 2nd time, got the usual error message. __ Tracker [EMAIL PROTECTED]