runner called waitress-serve, which can be used in development and in situations where the likes of PasteDeploy is not necessary: # Listen on both IPv4 and IPv6 on port 8041 waitress-serve --listen=*:8041 --listen=*:8041 myapp:wsgifunc # Listen on only IPv4 on port 8041 waitress-serve --port=8041 myapp:wsgifunc 1.1.1 Heroku Waitress can be used to serve WSGI apps on Heroku, include waitress in your requirements requirements.txt file a update the Procfile as following: web: waitress-serve \ --listen "*:$PORT" \ --trusted-proxy '*' \ --trusted-proxy-headers 'x-forwarded-for x-forwarded-proto x-forwarded-port' \ --log-un

runner called waitress-serve, which can be used in development and in situations where the likes of PasteDeploy is not necessary: # Listen on both IPv4 and IPv6 on port 8041 waitress-serve --listen=*:8041 --listen=*:8041 myapp:wsgifunc # Listen on only IPv4 on port 8041 waitress-serve --port=8041 myapp:wsgifunc 1.1.1 Heroku Waitress can be used to serve WSGI apps on Heroku, include waitress in your requirements requirements.txt file a update the Procfile as following: web: waitress-serve \ --listen "*:$PORT" \ --trusted-proxy '*' \ --trusted-proxy-headers 'x-forwarded-for x-forwarded-proto x-forwarded-port' \ --log-un

runner called waitress-serve, which can be used in development and in situations where the likes of PasteDeploy is not necessary: # Listen on both IPv4 and IPv6 on port 8041 waitress-serve --listen=*:8041 --listen=*:8041 myapp:wsgifunc # Listen on only IPv4 on port 8041 waitress-serve --port=8041 myapp:wsgifunc For more information on this, see waitress-serve. 1.2 Access Logging The WSGI design is modular. Waitress wrapper that wraps a sufficiently file-like object. It may do something fancier in the future. 1.9 waitress-serve New in version 0.8.4: Waitress comes bundled with a thin command-line wrapper around the waitress

runner called waitress-serve, which can be used in development and in situations where the likes of PasteDeploy is not necessary: # Listen on both IPv4 and IPv6 on port 8041 waitress-serve --listen=*:8041 --listen=*:8041 myapp:wsgifunc # Listen on only IPv4 on port 8041 waitress-serve --port=8041 myapp:wsgifunc 1.1.1 Heroku Waitress can be used to serve WSGI apps on Heroku, include waitress in your requirements requirements.txt file and update the Procfile as following: web: waitress-serve \ --listen "*:$PORT" \ --trusted-proxy '*' \ --trusted-proxy-headers 'x-forwarded-for x-forwarded-proto x-forwarded-port' \ --log-

runner called waitress-serve, which can be used in development and in situations where the likes of PasteDeploy is not necessary: # Listen on both IPv4 and IPv6 on port 8041 waitress-serve --listen=*:8041 --listen=*:8041 myapp:wsgifunc # Listen on only IPv4 on port 8041 waitress-serve --port=8041 myapp:wsgifunc For more information on this, see waitress-serve. Logging waitress.serve calls logging.basicConfig() Differences from zope.server waitress API Arguments to waitress.serve Support for wsgi.file_wrapper waitress-serve Glossary Change History 1.1.0 (2017-10-10) Features Waitress now has a __main__ and thus

Differences from zope.server waitress API Arguments to waitress.serve Support for wsgi.file_wrapper waitress-serve Socket Activation Glossary Change History 2.1.1 Security Bugfix Waitress now validates that now compatible with WSGIServer pre-0.8.4. 0.8.4 (2013-05-24) Add a command-line runner called waitress-serve to allow Waitress to run WSGI applications without any addional machinery. This is essentially runner called waitress-serve, which can be used in development and in situations where the likes of PasteDeploy is not necessary: # Listen on both IPv4 and IPv6 on port 8041 waitress-serve --listen=*:8041

Differences from zope.server waitress API Arguments to waitress.serve Support for wsgi.file_wrapper waitress-serve Socket Activation Glossary Change History 2.1.0 Python Version Support Python 3.6 is no longer now compatible with WSGIServer pre-0.8.4. 0.8.4 (2013-05-24) Add a command-line runner called waitress-serve to allow Waitress to run WSGI applications without any addional machinery. This is essentially runner called waitress-serve, which can be used in development and in situations where the likes of PasteDeploy is not necessary: # Listen on both IPv4 and IPv6 on port 8041 waitress-serve --listen=*:8041

runner called waitress-serve, which can be used in development and in situations where the likes of PasteDeploy is not necessary: # Listen on both IPv4 and IPv6 on port 8041 waitress-serve --listen=*:8041 --listen=*:8041 myapp:wsgifunc # Listen on only IPv4 on port 8041 waitress-serve --port=8041 myapp:wsgifunc For more information on this, see waitress-serve. 1.2 Access Logging The WSGI design is modular. Waitress wrapper that wraps a sufficiently file-like object. It may do something fancier in the future. 1.9 waitress-serve New in version 0.8.4: Waitress comes bundled with a thin command-line wrapper around the waitress

Differences from zope.server waitress API Arguments to waitress.serve Support for wsgi.file_wrapper waitress-serve Socket Activation Glossary Change History 3.0.1 (unreleased) Fix a bug that would lead to now compatible with WSGIServer pre-0.8.4. 0.8.4 (2013-05-24) Add a command-line runner called waitress-serve to allow Waitress to run WSGI applications without any addional machinery. This is essentially runner called waitress-serve, which can be used in development and in situations where the likes of PasteDeploy is not necessary: # Listen on both IPv4 and IPv6 on port 8041 waitress-serve --listen=*:8041

Differences from zope.server waitress API Arguments to waitress.serve Support for wsgi.file_wrapper waitress-serve Socket Activation Glossary Change History 1.4.0 (2019-12-20) Bugfixes Waitress used to slam now compatible with WSGIServer pre-0.8.4. 0.8.4 (2013-05-24) Add a command-line runner called waitress-serve to allow Waitress to run WSGI applications without any addional machinery. This is essentially runner called waitress-serve, which can be used in development and in situations where the likes of PasteDeploy is not necessary: # Listen on both IPv4 and IPv6 on port 8041 waitress-serve --listen=*:8041