If you want to do this, I wonder is this possible to do with the
timeline RSS view? You could use the timeline RSS on ticket updates + a
custom XSLT to do this without scripting. Below is an example that may
be useful for you based on the Trac site itself.

http://trac.edgewall.org/timeline?ticket=on&ticket_details=on&max=50&day
sback=7&format=rss

If you only want part of the information (for example, just simply
literally a list of changed ticket numbers in the last week), you can
parse the XML easily. I noticed in the Trac timeline view that all of
the titles in the XML have the same form:

Ticket #6072 (task updated): wrap email addresses

It probably wouldn't be hard at all to parse these to get all of the
information you need using a regexp. Of course, this interface to Trac
will be brittle but requires less knowledge of the internals and doesn't
require Python.

Jason

________________________________________
From: Nick Aschberger

Sure, unfortunately my IRC ports are blocked...

Anyway, what I want to do is as follows:
Previously we have had scripting that queried a DDTS database to grab
information about all tickets that had been updated in the last week.
This data was formatted and used to create a template for meeting
minutes, so tickets could be discussed each week.

We've moved to Trac now, which is nicer, but I would like to update the
existing scripting to work with trac.
So, I need my scripting to be able to grab that information from the
Trac database, I was hoping there was some sort of command line
interface to Trac which would do this.

If there is a python API only, then I could work with that.

cheers

Nick

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to