Regression: No support for cheroot WSGI server

[Juerg Haefliger]

Python3-bottle used to support the WSGI server provided by CherryPy (python3-cherrypy3). But since Jammy CherryPy (>=9) no longer provides a WSGI server, instead Cheroot (python3-cheroot) is supposed to be used (which also comes from the CherryPy project). Bottle in Jammy does not support Cheroot. Can we upgrade that package to at least version 0.12.21-1 (currently in Kinetic) which does support Cheroot so that previous CherryPy WSGI server users can more easily switch to Cheroot?

The changes between 0.12.19 (Jammy) and 0.12.21 (Kinetic) are mostly only adding support for cheroot (plus bugfixes).

From https://github.com/bottlepy/bottle:

a1cf80f96afe (tag: 0.12.21) Release of 0.12.21
d21578043dad Fix: Bad deprecation warning in cherrypy server adapter
a2b0ee6bb4ce (tag: 0.12.20) Release of 0.12.20
e140e1b54da7 Gracefully handle errors during early request binding.
6e9c55ac2599 Added depr warning for the outdated cherrypy server adapter.
a3ba0eb30e7b Added 'cheroot' server adapter to list of server names, so it can be selected from the command line and by name.
888aa8e7b8f6 Add ServerAdapter for CherryPy >= 9
e1be22df61b9 Fix for Issue #586
ed32f36b3feb Fix: Multipart file uploads with empty filename not detected as binary.
152219818378 (tag: 0.12.19) Release of 0.12.19

[Dimitri John Ledkov (xnox)]

I am assuming that python-cheroot 8.5.2+ds1-1ubuntu3 is good enough in jammy

[Dimitri John Ledkov (xnox)]

This looks like a release regression of core functionality not working.
It would be nice if there was an autopkgtest that uses wsgi, such that this loss of functionality would have been identified during jammy development release.
The upstream changes do appear to be bugfixes to address this feature loss / compatibility issue, rather than any substantial feature work.