On Mon, Jan 14, 2019 at 8:35 PM Volker Braun wrote:
>
> So I take it you volunteer to maintain the py3 buildbot configuration?
No, I do not. It's not my buildbot and I don't have control over that
infrastructure as your follow-up message makes clear:
> The buildbot physically moved this week, i
So I take it you volunteer to maintain the py3 buildbot configuration?
On Monday, January 14, 2019 at 11:45:20 AM UTC+1, E. Madison Bray wrote:
>
> In fact I'd argue it doesn't even require a Makefile target,
> as the relevant buildbot(s) for Python 3 can be configured to run that
> command (th
On Sun, Jan 13, 2019 at 5:18 PM Volker Braun wrote:
>
> Frederic, if can you make #26740 work then I'll merge it (no matter what Eric
> says ;-)
As I last pointed out on that ticket it doesn't even require any code
changes. In fact I'd argue it doesn't even require a Makefile target,
as the rel
Le dimanche 13 janvier 2019 09:25:39 UTC+1, Dima Pasechnik a écrit :
>
> Let us have the next release staring with merging all the positively
> reviewed py3 tickets.
> Right now it is very hard to see why a paricular change introduces a py3
> problem, as there are so many changes that need be mer
Let us have the next release staring with merging all the positively
reviewed py3 tickets.
Right now it is very hard to see why a paricular change introduces a py3
problem, as there are so many changes that need be merged.
On Sun, 13 Jan 2019 at 08:13, wrote:
> This is the second consecutive bet
