2017-02-02 22:24 GMT+01:00 Maciej Szulik :
> Ezio confirmed pushing all the changes to bugs.python.org already.
> I'm very sorry for all the inconvenience caused by previous mistakes. If
> your
> issues was closed make sure to verify it was closed properly and re-open if
> needed.
Don't worry. Bre
On Thu, Feb 2, 2017 at 6:01 PM, Victor Stinner
wrote:
> 2017-02-01 18:32 GMT+01:00 Victor Stinner :
> > To finish with an empty change:
>
> Information on IRC:
>
> Known issue: http://psf.upfronthosting.co.za/roundup/meta/issue611
>
> "Maciej is working on it"
>
> Good & thanks!
>
>
I just fixed
2017-02-01 18:32 GMT+01:00 Victor Stinner :
> To finish with an empty change:
Information on IRC:
Known issue: http://psf.upfronthosting.co.za/roundup/meta/issue611
"Maciej is working on it"
Good & thanks!
Victor
___
Python-Dev mailing list
Python-De
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
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: rejec
