Pablo Galindo Salgado <pablog...@gmail.com> added the comment:
Background on why I reactivated it: I every single alpha release I had to fix actual documentation errors (no false positives) like the one fixed here: https://github.com/python/cpython/commit/20ac34772aa9805ccbf082e700f2b033291ff5d2 I don't like the check, but the release management team don't like to have to restart the release process just fo fix a bunch of docs issues that should have been detected by the CI. If we remove the fix, we need to coordinate all together because currently the status quo is that the RM team now is responsable of fixing the documentation errors as there are several release tools (and other ones) that depend on this target passing. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue42238> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
