Pablo Galindo Salgado <pablog...@gmail.com> added the comment:
> Why did you catch them in the release process, and not in the regular Python > development workflow? Because our release tools run suspicious.py and it fails and then we need to manually inspect every single failure and fix it as almost all times there are real positives among them > Can't we get the same errors in the regular workflow? That's what I did reactivating suspicious.py > I understand that the release process requires no warning from "make > suspicious", but as explained in other comments, this tool is not reliable. > While it catchs some real bugs, the cost of false positives is too high Sure, we all agree here. Where it seems that we don't agree is how to proceed. I would be super happy to remove the tool if is agreed everywhere, including with the rest of release managers. ---------- _______________________________________ 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
