root/notes.txt

Launchpad

<bradb> seb128: If he's using Python, then the two things that immediately come to mind are mechanize and BeautifulSoup. They're a decent API to avoid having to write screen-scraping code directly. The query and manipulation xmlrpc APIs won't be ready in a practical time frame for the SoC student, I don't think.
<seb128> <bradb> seb128: I see no obvious reason why we can't include the description in +text (to fix 51835). No idea about 51836, but I imagine it can be fixed.
<seb128> <bradb> seb128: But with the modules I mentioned earlier, and a bit of creativity (e.g. you can get the description from +edit), there is a way to keep moving forward, even in the worst case if nothing changed.


Gnome Bugzilla

<bkor> ploum: basically for show_bug.cgi you can add &ctype=xml to get XML output
<ploum> aaaah ! that's great !
<bkor> ploum: with &field= you can control exactly what fields to see.. or use &excludefield to not display certain fields
<bkor> however, do NOT use this on many bugs.. it will slow the server down
<-- bandini a quitté (Ex-Chat)
<ploum> bkor: thanks a lot
<bkor> for multiple bugs, use: http://bugzilla.gnome.org/show_bug.cgi?id=163163&id=163164&excludefield=long_desc&ctype=xml

for searches
<bkor> seems not, only &ctype= js/csv/html/ics/rdf/atom  (basically everything except the one you want)
<bkor> rdf might be useful
<bkor> oh, btw.. be careful with RDF.. it existed in some versions, but they replaced it with Atom as RDF spec was unclear about certain things
<bkor> so in certain Bugzilla versions, when you request RDF, you will get Atom..
<bkor> as Atom was added later, you might get a error if you request atom specifically (stupid mess)
<bkor> with &columnlist=stuff you should be able to control what fields buglist.cgi returns
<bkor> (check 'Change Columns' or something like that under a b.g.o query result)