Closed tschorr closed 5 years ago
@tschorr thanks for creating this Pull Request and help improve Plone!
To ensure that these changes do not break other parts of Plone, the Plone test suite matrix needs to pass.
Whenever you feel that the pull request is ready to be tested, either start all jenkins jobs pull requests by yourself, or simply add a comment in this pull request stating:
@jenkins-plone-org please run jobs
With this simple comment all the jobs will be started automatically.
Happy hacking!
@jenkins-plone-org please run jobs
@jenkins-plone-org please run jobs
@jenkins-plone-org please run jobs
Hm, there are broken tests, I'd like to review after they are fixed.
There are broken doctests after merging master. I'm about to fix them. Don't merge
@jenkins-plone-org please run jobs
@icemac Travis tests are green now and the one failing Robot Test on Jenkins looks unrelated. Feel free to review.
@jensens I currently don't have an opportunity to test this on Windows
@icemac I'm basically following https://pastedeploy.readthedocs.io/en/latest/#paste-server-factory. I opted for import waitress
and waitress.serve
to avaoid the ambiguity.
@jenkins-plone-org please run jobs
Again the one failing robot test looks unrelated.
Indeed, I merge this one now.
s. https://github.com/plone/plone.recipe.zope2instance/issues/71 (and also https://github.com/zopefoundation/Zope/issues/416).
waitress.serve() accepts a list of (prebound) sockets, https://waitress.readthedocs.io/en/latest/arguments.html.
Suggestion is to bind a socket before loading the application and to use a custom server_factory to make this work with PasteDeploy. This could also be done in https://github.com/zopefoundation/Zope, but plone.recipe.zope2instance is already relying on waitress anyway (Zope doesn't really seem to depend on waitress even though it is currently required it in it's setup.py).