On Oct 20, 9:45 am, "Trevor Johns" <[EMAIL PROTECTED]> wrote: > > First off, please don't try to tokenize URLs and extract things at > specific locations. This is a recipe to have things break later on > should we change where resources are mapped. > > The /allcalendars feed exposes the feed URL for an individual calendar > as a link element taking the following form: > > <link rel="alternate" type="application/atom+xml" href="..."> > > Use the contents of that href attribute as your URL. > > When using the Python client library, you can retrieve this by calling > e.GetAlternateLink().href. Since this is the complete feed URL for the > corresponding calendar, you won't need to do any string manipulation.
Thank you for the tip, it was a huge mistake the way I was working. I think I saw this (http://groups.google.com/group/google-calendar-help- dataapi/browse_thread/thread/c2590f44a2c8ace1/38403eaaeeaaf160? lnk=gst&q=create+event+non+default#38403eaaeeaaf160) and I was missing the url given by GetAlternateLink. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
