Refactor wsgiserver to simplify the use of m2crypto (if one so chooses)
The bind method of CherryPyWSGIServer is very monolithic. In my case, I have to use m2crypto instead of pyopenssl, and that means I have to override the whole function. If the function was broken down into logical steps, it would be much easier to achieve that.
Attached is a proposal (which also moves the dual-stack activation before the SSL setup, see
Reported by firstname.lastname@example.org