Simon Glass sjg@chromium.org writes:
Hi Daniel,
On Sun, 5 Jul 2020 at 22:50, Daniel Axtens dja@axtens.net wrote:
Daniel Axtens dja@axtens.net writes:
Hi Simon,
I can't see a cover letter so apologies if I've misunderstood something basic, but this doesn't appear to apply to the patchwork tree - I'm guessing the patchwork relevance is with regards to the last few patches that (AFAICT) parse the patchwork web interface for information?
Ah, nevermind, the cover letter got caught in moderation. I've released it.
pwclient speaks the old, less documented XML-RPC API. We have a new REST API which is much better documented, and is explorable (e.g. https://patchwork.ozlabs.org/api/ and https://patchwork.readthedocs.io/en/latest/api/rest/ )
I haven't fully digested the patches (and I lack a lot of context) but is there a reason the patchwork API isn't able to meet your needs here? (And if so, could we extend it rather than having you parse the frontend?)
So these questions still stand but for the REST API.
So use the REST API instead of the web page? That sounds fine to me. Is it generally enabled on patchwork servers?
I mean patman is your code so it's ultimately not my call :P But yes, I'd strongly prefer you used the REST API! It is enabled on ozlabs.org and kernel.org and has been for a while (~a couple of years).
What is the status of pwclient? Is it dead? Is there a replacement? I'd love to use a Python library if one exists.
Stephen F is the expert on the client stuff, so I'm not going to make a call on the status of pwclient. All I am confident to say is that I have migrated to using 'git-pw' and I recommend others do so to too.
I'm not sure if a dedicated Python client library exists: the last time I wanted to write a Python client app I found it simple enough to just use the JSON that the API provides directly. But the place I'd start with is git-pw.
Regards, Daniel
Regards, SImon