Jason R. Coombs
Jason R. Coombs
Unfortunately, the current workflow is not working for me or for this project. The current release process is manual and opaque and this project is becoming unmaintained. It's been over...
I'm not just concerned with the release workflow. I'm concerned about all of the other concerns that jaraco/skeleton addresses (unified maintenance, integrated linting and type checking, Python versioning support, tooling...
See [cherrypy-dynpool](https://pypi.python.org/pypi/cherrypy-dynpool) for a project that implements a dynamic thread pool. Contributions to improve the implementation or have the documentation match the implementation are also welcome.
I get these same failures on my workstation.
When I run the tests on Python 3.9, I get a different failure, but none of those reported above.
It looks like maybe this issue was encountered in CI and suppressed there only (bff4985d1ade525a4f0fc9aea4c0bb7b8aef7572).
After expanding the xfail, the tests on Python 3.10 now fail the same as on 3.9 and 3.8.
My instinct is the same. If David is right and there are some 30k hosts running in Dev mode, perhaps there's something more that CherryPy should do to warn about...
I have no reason to think that it's not the case. I haven't tested it, though.
I haven't changed my password. I expected the upload to work. Today I manually uploaded the release (after working around several other obstacles). I've opened #226 to clear one of...