Hi, I noticed a strange issue with Roundup Robot on the issue #29318. I closed http://bugs.python.org/issue29318 as rejected: resolution: -> rejected status: open -> closed Roundup Robot made a first change: stage: -> resolved But then it made a second change: resolution: rejected -> fixed To finish with an empty change: => I got an email to notify me "Changes by Roundup Robot ", but with no useful email body. --- 8< --- Changes by Roundup Robot : _______________________________________ Python tracker http://bugs.python.org/issue29318 --- 8< --- Victor

Oh, I noticed another strange thing: The Roundup Robot closed the issue http://bugs.python.org/issue29368 but I don't see any explicit "Close issue #xxx" or "Close #xxx" in the commit message of the two commits. Is it deliberate to close an issue after any commit? Victor 2017-01-31 19:18 GMT+01:00 Brett Cannon :

I've activated the webhook for receiving comments on issues when a commit lands mentioning an issue, so if you see a commit from our hg integration and another from GitHub, understand that's why (mention issues as "bpo NNNN" in commit messages if you want to see it in action). If it becomes too much of a hassle to see the duplicates before we migrate I can turn off the notifications, but obviously more testing the better. :)

_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/victor.stinner%40gmail.co...