Waitress 2.0.0 Released

6 views
Skip to first unread message

Bert JW Regeer

unread,
Mar 9, 2021, 4:15:38 AM3/9/21
to Pylons Project, Pylons Project
Hey all,

Thanks for your patience, especially those of you who helped make this release happen. Waitress 2.0.0 is now ready to fetch from your closest cheese shop.

https://pypi.org/project/waitress/2.0.0/

Friendly Reminder

This release still contains a variety of deprecation notices about defaults that can be set for a variety of options.
Please note that this is your last warning, and you should update your configuration if you do NOT want to use the new defaults.
See the arguments documentation page for all supported options, and pay attention to the warnings:

https://docs.pylonsproject.org/projects/waitress/en/stable/arguments.html

Without further ado, here’s a short list of great changes thanks to our contributors!

Bugfixes/Features
• Fix a crash on startup when listening to multiple interfaces. See https://github.com/Pylons/waitress/pull/332
• Waitress no longer attempts to guess at what the server_name should be for a listen socket, instead it always use a new adjustment/argument named server_name.
Please see the documentation for server_name inhttps://docs.pylonsproject.org/projects/waitress/en/latest/arguments.html and see https://github.com/Pylons/waitress/pull/329
• Allow tasks to notice if the client disconnected.
This inserts a callable waitress.client_disconnected into the environment that allows the task to check if the client disconnected while waiting for the response at strategic points in the execution and to cancel the operation.
It requires setting the new adjustment channel_request_lookahead to a value larger than 0, which continues to read requests from a channel even if a request is already being processed on that channel, up to the given count, since a client disconnect is detected by reading from a readable socket and receiving an empty result.
See https://github.com/Pylons/waitress/pull/310
• Drop Python 2.7 and 3.5 support
• The server now issues warning output when it there are enough open connections (controlled by “connection_limit”), that it is no longer accepting new connections. This situation was previously difficult to diagnose. See https://github.com/Pylons/waitress/pull/322

Found a bug?

Please direct your closest browser over to https://github.com/Pylons/waitress/issues

Thanks,
Bert JW Regeer
Reply all
Reply to author
Forward
0 new messages