Steve Dower <steve.do...@python.org> added the comment:
The build for Windows is mostly automated, but it's triggered and monitored by hand. The build steps are all in the source repo, and the builds themselves are public at https://dev.azure.com/Python/cpython/_build?definitionId=21, but I'm the only core dev with access to the code signing certificate, so the only one who can trigger an official Windows release. More importantly though is that we stop validating all the dependencies (e.g. OpenSSL) against security-fix only releases. These are optional dependencies from the POV of CPython, but required for a binary release. Maintaining support for them isn't free, so dropping the binary releases means we can focus on our active releases, rather than on regularly reintegrating other people's projects. Otherwise we'd have to do a new release every time OpenSSL/libffi/Tk/Tcl/Sqlite3/etc. fixed a security issue. *That's* the cost we avoid by not releasing binaries, even though the cost of the build itself is pretty low these days. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue45079> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
