Brett Cannon added the comment: I'm not sure if this is going to be useful enough to force all contributors to deal with. Justification for a change should be on bugs.python.org and that's mentioned in the CONTRIBUTING.md guidelines. As for testing, the Travis/AppVeyor failures should communicate that. And for specifying the issue number, there's a status check for that to help communicate it.
I'll let other core devs comment, but while I appreciate what Jensen is trying to help with, I don't think the template helps enough to justify forcing every contributor to have to deal with it. You can also bring this up on the core-workflow mailing list, Jensen, if you want to discuss it there. ---------- nosy: +brett.cannon priority: normal -> low _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue30336> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
