Actually I found the answer: The timezone was in the times returned by the query all along, I just had not been parsing it. The standard python date-string parser does not understand timezone strings so I needed to get a better one.
:-) On May 6, 11:41 pm, Salim Fadhley <[EMAIL PROTECTED]> wrote: > Dear experts, > > I typically do google-calendar queries like this: > > query = gdata.calendar.service.CalendarEventQuery( self.username, > self.visibility, self.projection ) > query.orderby = "starttime" > query.singleevents = "true" > query.start_max = endTime.isoformat() > query.start_min = startTime.isoformat() > > This seems to interpret my start and end times as local-timezone - > unfortunately my application needs to be consistent and international. > Is it possible to make all queries (and responses) in UTC / GMT? So > when I send this query to Google Calendar I want google's machine to > understand that I am asking in UTC and I expect a response back with > all times in UTC? > > Alternatively, if I get back a set of events from a query, is it > possible to know which timezone any time information is specified in? > > Thanks --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Calendar Data API" 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/google-calendar-help-dataapi?hl=en -~----------~----~----~----~------~----~------~--~---
