On Tue, Sep 11, 2007 at 01:35:58PM +0200, Daniel Holbach wrote:
> bughelper and python-launchpad-bugs are now part of Ubuntu's
> infrastructure. We use these tools to
>
> * find certain classes of bugs
> * modify masses of bugs at the same time
> * file bugs
> * integrate small tools with Launchpad
>
> For python-launchpad-bugs to do its work, we parse Launchpad HTML. Even
> subtle changes break the code every now and then. We have to find them
> out manually.
The first question I have is: what's missing in the +text version of
the bug that leads you to parsing HTML? Here is a sample:
https://launchpad.net/bugs/1/+text
We also have a +bugs-text listing for searches, but that appears to be
non-functional (and I'm not sure why, but if you had been using it you'd
have complained by now :-)
> Still it'd be nice to have a way to understand UI changes better and to
> be aware of them. This includes new columns in tables, new required
> arguments for HTML forms and so on.
>
> What can we do to stay in the loop and not have to do work manually?
I doubt there's a way to avoid "manual work" if you are parsing HTML.
However, it is much easier for us to communicate updates to our
parseable exports; we could even version them conveniently.
--
Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 3376 0125
This is the launchpad-users mailing list archive — see also the general help for Launchpad.net mailing lists.
(Formatted by MHonArc.)