Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Errno 10035] A non-blocking socket operation could not be completed immediately on python 3.1.2 #69519

Closed
raghuprasad mannequin opened this issue Oct 7, 2015 · 5 comments
Labels
OS-windows type-bug An unexpected behavior, bug, or error

Comments

@raghuprasad
Copy link
Mannequin

raghuprasad mannequin commented Oct 7, 2015

BPO 25332
Nosy @pfmoore, @tjguk, @vadmium, @zware, @zooba

Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2015-10-07.21:56:15.618>
created_at = <Date 2015-10-07.10:48:40.504>
labels = ['type-bug', 'OS-windows']
title = '[Errno 10035] A non-blocking socket operation could not be completed immediately  on python 3.1.2'
updated_at = <Date 2015-10-07.21:56:15.617>
user = 'https://bugs.python.org/raghuprasad'

bugs.python.org fields:

activity = <Date 2015-10-07.21:56:15.617>
actor = 'zach.ware'
assignee = 'none'
closed = True
closed_date = <Date 2015-10-07.21:56:15.618>
closer = 'zach.ware'
components = ['Windows']
creation = <Date 2015-10-07.10:48:40.504>
creator = 'raghu prasad'
dependencies = []
files = []
hgrepos = []
issue_num = 25332
keywords = []
message_count = 5.0
messages = ['252463', '252465', '252475', '252486', '252487']
nosy_count = 6.0
nosy_names = ['paul.moore', 'tim.golden', 'martin.panter', 'zach.ware', 'steve.dower', 'raghu prasad']
pr_nums = []
priority = 'normal'
resolution = 'out of date'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue25332'
versions = ['Python 3.2']

@raghuprasad
Copy link
Mannequin Author

raghuprasad mannequin commented Oct 7, 2015

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):
                       getRequest.add_header("ServerContent",compName)
                       getRequest.add_header("Content-
                   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
https://hg.python.org/cpython/rev/8ec39bfd1f01

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

@raghuprasad raghuprasad mannequin added OS-windows type-bug An unexpected behavior, bug, or error labels Oct 7, 2015
@vadmium
Copy link
Member

vadmium commented Oct 7, 2015

According to bpo-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.

@raghuprasad
Copy link
Mannequin Author

raghuprasad mannequin commented Oct 7, 2015

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

@vadmium
Copy link
Member

vadmium commented Oct 7, 2015

See <https://bugs.python.org/issue9090#msg117549\>, 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.)

@zware
Copy link
Member

zware commented Oct 7, 2015

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.

@zware zware closed this as completed Oct 7, 2015
@ezio-melotti ezio-melotti transferred this issue from another repository Apr 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
OS-windows type-bug An unexpected behavior, bug, or error
Projects
None yet
Development

No branches or pull requests

2 participants