Hi all, On Sat, Jul 4, 2009 at 18:20, Sean Coates<s...@caedmon.net> wrote: >> so what i'm wondering is: is there an easily parseable or structured >> interface (xmlrpc, soap, read-only JSON export, whatever) to the php.net >> bts >> that could be used to get a bug's information? or would such a bts-link >> service need to resort to scraping the page for a particular bug's status? > > Not sure if this really helps you (and I agree that the bug system really > needs some sort of better programmatic interface), but you can translate > most bugs.php.net pages into rss (which is easier to parse than HTML... > usually (-: ) by prepending rss/ to the URL. This useful for reading. > > For example: > http://bugs.php.net/bug.php?id=46944 > becomes: > http://bugs.php.net/rss/bug.php?id=46944
yeah, I'll probably follow this way, but using the format=xml parameter: http://bugs.php.net/rss/bug.php?format=xml&id=46944 that seems better for programmatical parsing. Just another question: may you please list me all the possible 'Status' field values? In particular we are interested in those 'Status'es that identify the bug as closed and "wontfix". Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
