Jason R. Coombs

I've confirmed that [this line](https://github.com/cherrypy/cheroot/blob/02f7a17cbc98398def138c6ce42d8cd6487955dd/cheroot/connections.py#L192) is being reached and the value is `1`, so I would expect the socket objects to have 1-second timeouts. So why is the timeout not...

At some point, Jython was supported and worked fine. I've personally used CherryPy in Jython. I'd like to think it's one of the most accessible web frameworks. With the introduction...

I'm also having problems installing it, because (from what I can tell), pip is currently broken on Jython (on at least a couple of levels). I was able to use...

Or not - we could just say Jython is supported but not tested/maintained internally.

Following the hint about the socket backlog, and reading answers to [this question](http://stackoverflow.com/questions/2444459/python-sock-listen), I found if I change the `_cp_server.Server.socket_queue_size` to 25, the tests stop failing. Even at 24, the...

I'm not sure what the solution is here. Should CherryPy be able to accept these connections more quickly? Or should we bump the backlog? If bumping the backlog, should it...

~See also the upstream [issue36274](https://bugs.python.org/issue36274) which attempts to solve the issue with Python rather than have each project implement its own workaround.~

I see now that that upstream issue is about something else. This issue is specifically about ensuring a 400 (bad request) is returned for invalid requests instead of attempting to...

Given that the Cheroot tests are flaky, having additional test suite runners (Appveyor, GitHub Actions, Circle CI, Travis, ...) magnifies any flakiness. Until we can get the false positives or...

Running with `tox -e py27 -- -k test_server`, I'm able to replicate the behavior. On Python 3, the tests complete without a hitch.