This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Title: [Errno 10035] A non-blocking socket operation could not be completed immediately on python 3.1.2
Type: behavior Stage: resolved
Components: Windows Versions: Python 3.2
Status: closed Resolution: out of date
Dependencies: Superseder:
Assigned To: Nosy List: martin.panter, paul.moore, raghu prasad, steve.dower, tim.golden, zach.ware
Priority: normal Keywords:

Created on 2015-10-07 10:48 by raghu prasad, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Messages (5)
msg252463 - (view) Author: raghu prasad (raghu prasad) Date: 2015-10-07 10:48
On one machine we are facing this issue 

[Errno 10035] A non-blocking socket operation could not be completed immediately

We are using urllib.request.urlopen with some timeout value

sample code 

getRequest = urllib.request.Request(getUrl)
                   getRequest.add_header("SessionID", sessID)
                   if (compName != None):
                   getReqResp = urllib.request.urlopen(getRequest, xmlContent , TIME_OUT)

every time we do urlopen for get and post operations we are receiving this 10035 error 

i have searched a lot over the web for any work arounds 

i found one place where the issue got fixed in python 2.7

i have checked the changes , but the same chages are not visible in the python 3.1.2

so is it a bug or is there any workaround

we are having an issue based in this in our project

so any input / resolution will be greatly helpful
msg252465 - (view) Author: Martin Panter (martin.panter) * (Python committer) Date: 2015-10-07 11:46
According to Issue 9090, this was already fixed in 3.2 and 2.7. I think the 3.1 branch is closed. Are you seeing the same problem in newer version of Python, or just 3.1.2? If only 3.1.2, I think you may be on your own.
msg252475 - (view) Author: raghu prasad (raghu prasad) Date: 2015-10-07 15:19
HI Martin,

Thanks for the immediate reply
i m sure about the version 3.2 

we are using 3.1.2 in our project so thought if it was missed in this version

Oh if 3.1.2 is closed then its bad luck 

can you provide some inputs on how to proceed further on this 
i heard 2.7 and 3.1.2 are completely different codes 

Any help on this could be useful for us
msg252486 - (view) Author: Martin Panter (martin.panter) * (Python committer) Date: 2015-10-07 21:19
See <>, which is why I thought the problem should be fixed in 3.2. Specifically, that commit went into v3.2a3.

If you can demonstrate the problem exists in 3.4 or newer, you might be able to get more people interested in fixing it. (Not me however; I don’t have Windows.)
msg252487 - (view) Author: Zachary Ware (zach.ware) * (Python committer) Date: 2015-10-07 21:56
Python 3.1 is long since dead, and 3.1.2 isn't even the latest 3.1.  Is there a particular reason why you're using it?  I highly recommend upgrading to a newer Python, either 3.4.3 or 3.5.0.  3.5.0 if you're on anything newer than Windows XP, 3.4.3 if you're on XP or Server 2003.
Date User Action Args
2022-04-11 14:58:22adminsetgithub: 69519
2015-10-07 21:56:15zach.waresetstatus: open -> closed
resolution: out of date
messages: + msg252487

stage: resolved
2015-10-07 21:19:27martin.pantersetmessages: + msg252486
2015-10-07 15:19:29raghu prasadsetmessages: + msg252475
2015-10-07 11:46:37martin.pantersetnosy: + martin.panter
messages: + msg252465
2015-10-07 10:48:40raghu prasadcreate