Jason R. Coombs
Jason R. Coombs
Someone sent an email to `team@` requesting guidance. Let's get this issue fixed.
In my other projects, I rely on Tidelift for security disclosure. Probably CherryPy should too. I'm going to assume that for now, but webknjaz - if you have something else...
Feel free to change the process to your preference.
I'm abandoning this work, as it seems CherryPy has evolved too far from the upstream expectations for it to be useful. I am exploring replacing `black` with `ruff --format`, but...
That's interesting. I also observe that docs builds are failing recently (18.9.0 build failed in RTD). Curiously, the 18.8.0 release did build.
Closing as languishing. Feel free to address the comments and revive or re-open a new one.
It doesn't looks like there's been progress on those issues, so maybe cheroot should abandon `forked` or just disable those tests until forked gets fixed.
Unpininng pytest results in new errors.
Pinning to `pytest < 7.2` allows the tests to run, but only on Python 3.11 or earlier. Attempting to run pytest 7 on Python 3.12 fails with a DeprecationWarning.
I've pushed that branch to `refs/archive/feature/commands-api` and deleted it. Basically all it did was expose all of the registered commands. ```python import pkg_resources def install_commands(): globals().update( (ep.name, ep.load()) for ep...