On 15/12/17 15:29, David Malcolm wrote: > On Fri, 2017-12-15 at 10:16 +0100, Paulo Matos wrote: >> >> On 14/12/17 12:39, David Malcolm wrote: > > [...] > >>> It looks like you're capturing the textual output from "jv compare" >>> and >>> using the exit code. Would you prefer to import "jv" as a python >>> module and use some kind of API? Or a different output format? >>> >> >> Well, I am using a fork of it which I converted to Python3. Would you >> be >> open to convert yours to Python3? The reason I am doing this is >> because >> all other Python software I have and the buildbot use Python3. > > Done. > > I found and fixed some more bugs, also (introduced during my > refactoring, sigh...) >
That's great. Thank you very much for this work. >> I would also prefer to have some json format or something but when I >> looked at it, the software was just printing to stdout and I didn't >> want >> to spend too much time implementing it, so I thought parsing the >> output >> was just easier. > > I can add JSON output (or whatever), but I need to get back to gcc 8 > work, so if the stdout output is good enough for now, let's defer > output changes. > Agree, for now I can use what I already have to read the output of jv. I think I can now delete my fork and just use upstream jv as a submodule. -- Paulo Matos
