Public bug reported: See https://bitbucket.org/cherrypy/cherrypy/issue/1170/bug-in- check_port-running-python-33 for upstream bug description and patch, commited in source in 2012 in this commit: https://bitbucket.org/cherrypy/cherrypy/commits/9820107d4ffb8058fd507888f90e28c695f6b4c0.
Summary: « The new exception hierarchy in Python 3.3 has created a bug in check_port in process/servers.py. IOError and socket.error are both now aliases of OSError, so a check for socket.error wrongly catches the IOError that's thrown in the try block. » It pretty much makes cherrypy unusable with Python 3.3+ (3.4 shipped with trusty), since when you start a server, about 50 s later it shuts down because of « port not bound », when it really is. ** Affects: cherrypy3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cherrypy3 in Ubuntu. https://bugs.launchpad.net/bugs/1353896 Title: Bug with Python3 in wait_for_occupied_port/check_port not patched To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cherrypy3/+bug/1353896/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs