[issue16434] SocketServer call shutdown in the wrong way
R. David Murray added the comment: Given the lack of additional info from the OP, I'm closing this. -- nosy: +r.david.murray resolution: - not a bug stage: test needed - resolved status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16434 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16434] SocketServer call shutdown in the wrong way
Senthil Kumaran added the comment: Looks an invalid bug to me as well. request is a socket.socket object and has shutdown method taking a single argument. The error pasted in the report leads me to believe if the shutdown_request call is not thread-safe and it is ending up called shutdown method in the module instead of the proper shutdown method of the request object. -- nosy: +orsenthil status: pending - open ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16434 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16434] SocketServer call shutdown in the wrong way
Andrew Svetlov added the comment: Move to pending until additional info will be provided. Required short test to reproduce the problem. -- status: open - pending ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16434 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16434] SocketServer call shutdown in the wrong way
Andrew Svetlov added the comment: request should be socket.socket instance which definitely has shutdown method accepting socket.SHUT_WR. I guest the problem not in stdlib but in your code or maybe in the Paste (I'm not familiar with it, sorry). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16434 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16434] SocketServer call shutdown in the wrong way
Changes by Andrew Svetlov andrew.svet...@gmail.com: -- stage: needs patch - test needed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16434 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16434] SocketServer call shutdown in the wrong way
Changes by Andrew Svetlov andrew.svet...@gmail.com: -- nosy: +asvetlov ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16434 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16434] SocketServer call shutdown in the wrong way
Changes by Andrew Svetlov andrew.svet...@gmail.com: -- stage: - needs patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16434 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16434] SocketServer call shutdown in the wrong way
New submission from Erik Günther: I have a small development WSGI-server using PythonPaste and when shutting it down I somtimes get the following error on one or two threads: ---8--- Traceback (most recent call last): File /usr/lib/python2.7/threading.py, line 551, in __bootstrap_inner self.run() File /usr/lib/python2.7/threading.py, line 504, in run self.__target(*self.__args, **self.__kwargs) File /usr/lib/python2.7/SocketServer.py, line 586, in process_request_thread self.shutdown_request(request) File /usr/lib/python2.7/SocketServer.py, line 459, in shutdown_request request.shutdown(socket.SHUT_WR) TypeError: shutdown() takes exactly 0 arguments (1 given) -8- /usr/lib/python2.7/SocketServer.py: 8--- def shutdown_request(self, request): Called to shutdown and close an individual request. try: #explicitly shutdown. socket.close() merely releases #the socket and waits for GC to perform the actual close. request.shutdown(socket.SHUT_WR) except socket.error: pass #some platforms may raise ENOTCONN here self.close_request(request) -8-- So I recon its a bug... -- messages: 175152 nosy: Erik.Günther priority: normal severity: normal status: open title: SocketServer call shutdown in the wrong way type: crash versions: Python 2.7 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16434 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16434] SocketServer call shutdown in the wrong way
Changes by Erik Günther erik.gunt...@gmail.com: -- type: crash - behavior ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16434 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16434] SocketServer call shutdown in the wrong way
Erik Günther added the comment: Sorry forgot to tell in what versions.. Its in Ubuntu 12.04-1 Python version 2.7.3 Ubuntu package version: 2.7.3-0ubuntu3.1 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16434 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
