[issue12441] _GLOBAL_DEFAULT_TIMEOUT remains as an object() in HTTPConnection and the connection hangs

2021-05-07 Thread Senthil Kumaran
Senthil Kumaran added the comment: The _GLOBAL_DEFAULT_TIMEOUT usage is an established pattern with socket module. https://github.com/python/cpython/blob/main/Lib/socket.py#L805 This is not a bug and we don't have a good reproducible step mentioned in the report. -- resolution: ->

[issue12441] _GLOBAL_DEFAULT_TIMEOUT remains as an object() in HTTPConnection and the connection hangs

2013-12-17 Thread Serhiy Storchaka
Changes by Serhiy Storchaka storch...@gmail.com: -- stage: - test needed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12441 ___ ___

[issue12441] _GLOBAL_DEFAULT_TIMEOUT remains as an object() in HTTPConnection and the connection hangs

2011-07-17 Thread Senthil Kumaran
Senthil Kumaran sent...@uthcode.com added the comment: Would you like to give an example snippet (server+client) which can help reproduce this behavior? -- assignee: - orsenthil nosy: +orsenthil ___ Python tracker rep...@bugs.python.org

[issue12441] _GLOBAL_DEFAULT_TIMEOUT remains as an object() in HTTPConnection and the connection hangs

2011-06-29 Thread Juanjo Alvarez
New submission from Juanjo Alvarez juan...@gmail.com: I was testing a jsonrpc server using a small Python client. I noticed that sometimes when the RPC returned some long test, the response object returned by URLOpener.open(), in my case an HTTPResponse, would hang about 70% of the time when

[issue12441] _GLOBAL_DEFAULT_TIMEOUT remains as an object() in HTTPConnection and the connection hangs

2011-06-29 Thread Juanjo Alvarez
Juanjo Alvarez juan...@gmail.com added the comment: PS: This only happens to my on Windows XP, works perfectly under Linux. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12441 ___