On 10/29/10 8:33 AM, Martin Albrecht wrote:
Hi there,
in light of the recent discussion on that our Trac based system shows its age
compared to more awesome technologies I figured I might try to automate a few
more steps of my own Trac interaction.
For me almost the most annoying thing is to
1) export the patch
2) upload the patch (make sure to click the overwrite button)
3) add myself as an author (or reviewer if it's a reviewer patch)
4) toggle the needs_review state
Those steps could easily be automated by adding a function to hg_sage called
for instance push_patch().
For now I'm relying on parsing the HTML output to get stuff like the current
list of authors etc. which seems to be what everybody does (sage-apply-ticket
does the same). Is there a better way of doing this (getting information about
a patch), e.g. is there a way to make Trac spit out some machine readable
format which is more easily parsed? We could use that to implement a class
TracTicket which automatically fetches all the information and makes it
accessible in a convenient fashion.
Surely the xmlrpc interface, or something like that, would be more
natural than parsing the html:
http://trac-hacks.org/wiki/XmlRpcPlugin
It seems that Mike Hansen had some pretty cool ideas about how to use
that plugin.
Or maybe there's another plugin that makes things more natural:
http://trac-hacks.org/
Maybe just accessing the trac database directly might be less work and
more consistent than parsing the html.
Jason
--
Jason Grout
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
