From fabien.loison at kozea.fr Fri Aug 12 11:11:34 2011 From: fabien.loison at kozea.fr (Fabien LOISON) Date: Fri, 12 Aug 2011 11:11:34 +0200 Subject: [icalendar-dev] PATCH: fix uid generator in util.py Message-ID: <1313140295.16443.8.camel@localhost.localdomain> Hello! I done a small patch for some issues in icalendar: * I fixed the uid generator in util.py (and I removed tools.py that contained the same code...) * I fixed a test in prop.vGeo (issue with the float) * I fixed the licence in the setup.py Regards, -------------- next part -------------- A non-text attachment was scrubbed... Name: uid.diff Type: text/x-patch Size: 5279 bytes Desc: not available Url : http://codespeak.net/pipermail/icalendar-dev/attachments/20110812/28037c80/attachment-0001.bin From thadeusb at thadeusb.com Sun Aug 14 01:52:57 2011 From: thadeusb at thadeusb.com (Thadeus Burgess) Date: Sat, 13 Aug 2011 18:52:57 -0500 Subject: [icalendar-dev] Cannot get google calendar to import generated calendar Message-ID: Example output: https://ezbilltracker.com/api/ical.ics?api_key=c7345919cbae723ed6968ccb9a8beb710ace581c143ded07a4e989f4 When uploading it as an .ics file it says "Processed Zero Events", and when adding by url it just adds the calendar but not events. Evolution and Thunderbird can parse the calendar just fine. It also parses 99% from the ical parsers, the only warning is that version should come before product id. Any ideas? Code to generate above ical ------------------------------------------------- cal = Calendar() cal.add('version', '2.0') cal.add('prodid', '-//EZ Bill Tracker//') for bill in bills: event = Event() event.add('summary', '%s - $%f - %s' % (bill.payee.name, bill.amount_due, 'PAID' if bill.is_paid_in_full else 'Not Paid')) event.add('description', 'Bill is due on %s\n%s' % (bill.due_date.strftime('%Y-%m-%d'), bill.notes)) event.add('dtstart', bill.due_date) event.add('dtend', bill.due_date) event.add('dtstamp', bill.due_date) cal.add_component(event) raw_cal = cal.as_string() -- Thadeus -------------- next part -------------- An HTML attachment was scrubbed... URL: http://codespeak.net/pipermail/icalendar-dev/attachments/20110813/b25e822c/attachment.htm From rok.garbas at gmail.com Thu Aug 18 16:30:51 2011 From: rok.garbas at gmail.com (Rok Garbas) Date: Thu, 18 Aug 2011 16:30:51 +0200 Subject: [icalendar-dev] iCalendar future Message-ID: <4E4D221B.40508@gmail.com> Hey all, As part of plone.app.event[1] PLIP (recurrence events in Plone) we are in need of some parser/generator for RFC5545 (successor of RFC2445) to make ical export for our event system. So instead of going crazy and write our own parser/generator for RFC5545 we thought it would be easier just to update `icalendar` to latest valid RFC (2445 is obsolete anyway). That's why we: - migrated away from codespeak (its in read mode only and is shutting down) to github[2] - since last release was more then 2 years ago a lot of ppl started their own forks. we reviewed them and migrated bugfixes over. - we gathered documentation and using readthedocs.org service we are generating documentation on every push[3]. ofcourse documentation is not done, but its a nice starting point. - switch to tests using tox (this way we can test for all python version from 2.4 to 2.7 with one key, which we are also running on every push to github[4] - everything prepared for release of 2.2 all i need is permission on pypi (I already have them but I would like to hear some, "yes" from Max or Janitor/) . - here we would like to propose new release of icalendar which would be nothing more but applied bugfixes and would keep following RFC2445. - if there is no active maintainer which would work and steer this project forward i would volunteer to take the role of active maintainer and update it so that version 3.0 will be RFC 5545 compatible. While we wait for your answers/ideas we will work already towards RFC5545 compatibility. If/As maintainer I plan few changes: - review mailing list from last release to today to see if there are any patched to apply or some issues reported. - sort out the issue with licensing[5]. - continue using github/collective for code. - move discussion from codespeak mailing list to github issue tracker. - make it 5545 compatible, extend current documentation and improve coverage. - work towards python3 version (but this will mean some more internal changes). What I definitely don't want is to mess somebodies else plans. If there are plans for further work on icalendar project I would gladly participate. Email was sent also to all commiters from codespeak/svn. [1] http://dev.plone.org/plone/ticket/10886 [2] https://github.com/collective/icalendar [3] http://readthedocs.org/docs/icalendar/en/latest/ [4] https://jenkins.plone.org/job/icalendar [5] http://codespeak.net/pipermail/icalendar-dev/2010-August/000157.html -- Rok Garbas - http://www.garbas.si From rok.garbas at gmail.com Thu Aug 18 16:43:11 2011 From: rok.garbas at gmail.com (Rok Garbas) Date: Thu, 18 Aug 2011 16:43:11 +0200 Subject: [icalendar-dev] iCalendar future In-Reply-To: <4E4D236B.9060606@wiggy.net> References: <4E4D221B.40508@gmail.com> <4E4D236B.9060606@wiggy.net> Message-ID: <4E4D24FF.2070706@gmail.com> On 18/08/11 16:36, Wichert Akkerman wrote: > Hi, > > On 08/18/2011 04:30 PM, Rok Garbas wrote: >> >> - switch to tests using tox (this way we can test for all python >> version from 2.4 to 2.7 with one key, which we are also running on >> every push to github[4] > > Why not use the jenkins configuration matrix logic to do this? I find > that to give much more intuitive results, and it removes the need for > all the tox complexity in packages. See > http://jenkins.simplon.biz/job/pyrad for example. > it is using configuration matrix. but uses tox as a runner. basically you create tox.ini with:: [tox] envlist = py24,py25,py26,py27 [testenv] deps = commands = and ofcourse you can get more specific. then run tox and it will run tests for all python's locally. and then you also setup the matrix with same setup. well in case you are interested :) > Other than that bit of bikeshedding I have no real comments except: go > for it. > tnx -- Rok Garbas - http://www.garbas.si From regebro at gmail.com Fri Aug 19 08:27:32 2011 From: regebro at gmail.com (Lennart Regebro) Date: Fri, 19 Aug 2011 08:27:32 +0200 Subject: [icalendar-dev] iCalendar future In-Reply-To: <4E4D221B.40508@gmail.com> References: <4E4D221B.40508@gmail.com> Message-ID: On Thu, Aug 18, 2011 at 16:30, Rok Garbas wrote: > [Cunning plan] Sounds good, go for it. > ?- work towards python3 version (but this will mean some more internal > changes). If I remember correctly, it will require the deprecation of using __str__() as an API, to be replaced with some other method. I gave up when I realized this, I didn't feel like making those kinds of changes then, they are pretty big. Some warning will need to be printed to the effect of "Generating iCalendar data by calling str() or .__str__() has been deprecated as this will break in Python 3. Please instead use .whatever()." Then it can be ported to Python 3. //Lennart From maxm at mxm.dk Fri Aug 19 10:27:33 2011 From: maxm at mxm.dk (Max M Rasmussen) Date: Fri, 19 Aug 2011 10:27:33 +0200 Subject: [icalendar-dev] iCalendar future In-Reply-To: References: <4E4D221B.40508@gmail.com> Message-ID: I have not heard the rest of this discussion. Just received this single mail. From "icalendar-dev at codespeak.net" I presume. But as the original developer of this package I feel a twinge of guilt that I have just left it out there, not updating it. But I have not written calendar software for a while, and I don't think I ever will again. So my motivation is not all that. I am just glad that somebody takes over the package, and it is with my full blessing that you take decisions without me. Just in case anybody cares or was in doubt :-D /Max 2011/8/19 Lennart Regebro > On Thu, Aug 18, 2011 at 16:30, Rok Garbas wrote: > > [Cunning plan] > > Sounds good, go for it. > > > - work towards python3 version (but this will mean some more internal > > changes). > > If I remember correctly, it will require the deprecation of using > __str__() as an API, to be replaced with some other method. I gave up > when I realized this, I didn't feel like making those kinds of changes > then, they are pretty big. Some warning will need to be printed to the > effect of "Generating iCalendar data by calling str() or .__str__() > has been deprecated as this will break in Python 3. Please instead use > .whatever()." > > Then it can be ported to Python 3. > > //Lennart > _______________________________________________ > icalendar-dev mailing list > icalendar-dev at codespeak.net > http://codespeak.net/mailman/listinfo/icalendar-dev > -- hilsen/regards Max M, Denmark http://www.mxm.dk/ IT's Mad Science Phone: +45 66 11 84 94 Mobile: +45 29 93 42 96 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://codespeak.net/pipermail/icalendar-dev/attachments/20110819/dd07a2b9/attachment.htm From faassen at startifact.com Fri Aug 19 11:43:11 2011 From: faassen at startifact.com (Martijn Faassen) Date: Fri, 19 Aug 2011 11:43:11 +0200 Subject: [icalendar-dev] iCalendar future In-Reply-To: <4E4D221B.40508@gmail.com> References: <4E4D221B.40508@gmail.com> Message-ID: Hey, +1 on all of this, sounds good. Glad someone is maintaining icalendar! Regards, Martijn From lupa at zurven.com Fri Aug 19 14:15:13 2011 From: lupa at zurven.com (Lupa Zurven) Date: Fri, 19 Aug 2011 08:15:13 -0400 Subject: [icalendar-dev] iCalendar future In-Reply-To: References: <4E4D221B.40508@gmail.com> Message-ID: +1 from my corner too. Am glad to see movement in this direction, albeit in the second decade of the 21st century. I, like Max, am no longer coding calendar software actively, but it's good to see such movement in the community. Cheers! +lupa+ On Fri, Aug 19, 2011 at 5:43 AM, Martijn Faassen wrote: > Hey, > > +1 on all of this, sounds good. Glad someone is maintaining icalendar! > > Regards, > > Martijn > _______________________________________________ > icalendar-dev mailing list > icalendar-dev at codespeak.net > http://codespeak.net/mailman/listinfo/icalendar-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://codespeak.net/pipermail/icalendar-dev/attachments/20110819/6dbe9c6d/attachment.htm From Georger at cozi.com Sat Aug 20 00:55:25 2011 From: Georger at cozi.com (George Reilly) Date: Fri, 19 Aug 2011 22:55:25 +0000 Subject: [icalendar-dev] iCalendar future In-Reply-To: Message-ID: +1 also. Thanks for picking up the baton, Rok. Unlike some of the others on this thread, Cozi is still actively developing calendar software. I see Rok picked up the fixes from our fork. Excellent! We've long used icalendar to parse iCalendar feeds. Recently, I used it to generate feeds, and I found several shortcomings, especially in VTIMEZONE handling. Unfortunately, expediency led me to work around this outside the icalendar code, instead of fixing icalendar. I hope to get a chance to do it right someday, but I'm awfully busy right now. -- /George V. Reilly ? Cozi ? Software Development Lead ? m: 206 730-8474 GeorgeR at cozi.com ? www.cozi.com ? blogs.cozi.com/tech I?m a Guinness World Record Holder! See the duckumentary From: Lupa Zurven > Date: Fri, 19 Aug 2011 08:15:13 -0400 To: Rok Garbas > Cc: Andreas Zeidler >, Wichert Akkerman >, Sidnei da Silva >, Johannes Raggam >, >, Faassen > Subject: Re: [icalendar-dev] iCalendar future +1 from my corner too. Am glad to see movement in this direction, albeit in the second decade of the 21st century. I, like Max, am no longer coding calendar software actively, but it's good to see such movement in the community. Cheers! +lupa+ On Fri, Aug 19, 2011 at 5:43 AM, Martijn Faassen > wrote: Hey, +1 on all of this, sounds good. Glad someone is maintaining icalendar! Regards, Martijn _______________________________________________ icalendar-dev mailing list icalendar-dev at codespeak.net http://codespeak.net/mailman/listinfo/icalendar-dev _______________________________________________ icalendar-dev mailing list icalendar-dev at codespeak.net http://codespeak.net/mailman/listinfo/icalendar-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://codespeak.net/pipermail/icalendar-dev/attachments/20110819/f3f00c09/attachment-0001.htm From egli at allink.ch Mon Aug 22 10:18:03 2011 From: egli at allink.ch (Marc Egli) Date: Mon, 22 Aug 2011 10:18:03 +0200 Subject: [icalendar-dev] Daylight saving time bug Message-ID: <991A7C77-7F42-4855-A1B1-3A9ED9F58971@allink.ch> hi there I've also encoutered the daylight saving time bug. I think we could fix this by using the following patch --- prop.py +++ (clipboard) @@ -309,7 +309,7 @@ def ical(self): if self.dt.tzinfo: - utc_time = self.dt - self.dt.tzinfo.utcoffset(self.dt) + utc_time = self.dt - self.dt.tzinfo.utcoffset(datetime.now()) return utc_time.strftime("%Y%m%dT%H%M%SZ") return self.dt.strftime("%Y%m%dT%H%M%S") i found the bug by trying the following in a python shell: >>> l=LocalTimezone(datetime.datetime(2011, 12, 23, 13,30)) >>> l CET >>> date=datetime.datetime(2011, 12, 23, 13,30) >>> date.replace(tzinfo=l) datetime.datetime(2011, 12, 23, 13, 30, tzinfo=CET) >>> l.utcoffset(datetime.datetime.now()) datetime.timedelta(0, 7200) >>> l.utcoffset(date) datetime.timedelta(0, 3600) >>> datetime.datetime.now() datetime.datetime(2011, 8, 22, 10, 14, 40, 272260) utcoffset respects the date and knows when to use daylight saving time. therefore we should use the actual date when evaluating the utcoffset marc From coriandergrrl at gmail.com Wed Aug 24 20:56:47 2011 From: coriandergrrl at gmail.com (Cori) Date: Wed, 24 Aug 2011 11:56:47 -0700 Subject: [icalendar-dev] Extracting private extension values in full form Message-ID: Hi, How would one go about extracting the non-standard properties (ie the X- named extensions) allowed by the iCalendar format? (non-standard properties: http://tools.ietf.org/html/rfc5545#section-3.8.8.2 ) I'd like to get the full property value when it's in the form: examples: BEGIN:VEVENT UID:134324 DTSTART;TZID=America/Los_Angeles:20070823T113000 X-RECURRENCE-ID:1334 X-MY-CUSTOMFIELD;NAME="Category";ID=10950;TYPE=SingleLine:Arts X-MY-CUSTOMFIELD;NAME="Cost";ID=10950;TYPE=SingleLine:Free END:VEVENT Thanks, Cori -------------- next part -------------- An HTML attachment was scrubbed... URL: http://codespeak.net/pipermail/icalendar-dev/attachments/20110824/ce56caf6/attachment.htm From sappj at ieee.org Wed Aug 24 22:07:13 2011 From: sappj at ieee.org (Joe Sapp) Date: Wed, 24 Aug 2011 16:07:13 -0400 Subject: [icalendar-dev] Extracting private extension values in full form In-Reply-To: References: Message-ID: <4E5559F1.6090809@ieee.org> On Wed 24 Aug 2011 02:56:47 PM EDT, Cori wrote: > Hi, > > How would one go about extracting the non-standard properties (ie the X- named > extensions) allowed by the iCalendar format? > (non-standard properties: http://tools.ietf.org/html/rfc5545#section-3.8.8.2) Hi, I don't think icalendar supports RFC 5545 yet, just 2445. See http://codespeak.net/pipermail/icalendar-dev/2011-August/000181.html for future plans. -- Joe Sapp From rok.garbas at gmail.com Wed Aug 24 23:28:44 2011 From: rok.garbas at gmail.com (Rok Garbas) Date: Wed, 24 Aug 2011 23:28:44 +0200 Subject: [icalendar-dev] iCalendar future In-Reply-To: References: <4E4D221B.40508@gmail.com> Message-ID: <4E556D0C.4060807@gmail.com> On 19/08/11 10:27, Max M Rasmussen wrote: > I have not heard the rest of this discussion. Just received this single > mail. From "icalendar-dev at codespeak.net > " I presume. > sorry i think i've missed you when compiling an email together. what a mistake ... and your the original author :) sorry > But as the original developer of this package I feel a twinge of guilt > that I have just left it out there, not updating it. > > But I have not written calendar software for a while, and I don't think > I ever will again. So my motivation is not all that. > > I am just glad that somebody takes over the package, and it is with my > full blessing that you take decisions without me. > > Just in case anybody cares or was in doubt :-D > Glad you all agree and nobody objects. So much easier to put time into coding then to convincing :) Max: would it be possible to update current "home"[1] with "iCalendar for python moved to github" - (issue 3 [5]) Martijn (or Max): as i see you are admin for this list. would it be possible to make it read only (no further mails can be sent to it). i plan to take discussion to github issue tracker[2]. (issue 4 [6]) To _all_ commiters (Max M., Andreas Zeidler, Lennart Regebro, Martijn Fassen, Sidnei da Silva, Wichert Akkerman, Pavel Repin, Eric Hanchrow, George V. Reilly, Johannes Raggam): would it be ok to license it as BSD[3]? i've opened an issue[4] for this so please send confirmation there on it there. also if you have any objection about the license i'm more then open to discuss them. i believe less restrictive And ... just did 2.2 release ... test it and report to the issue tracker. [1] http://codespeak.net/icalendar/ [2] http://github.com/collective/icalendar [3] http://www.opensource.org/licenses/bsd-license.php [4] https://github.com/collective/icalendar/issues/2 [5] https://github.com/collective/icalendar/issues/3 [6] https://github.com/collective/icalendar/issues/4 -- Rok Garbas - http://www.garbas.si -------------- next part -------------- A non-text attachment was scrubbed... Name: 0x9A8C3DC8.asc Type: application/pgp-keys Size: 3877 bytes Desc: not available Url : http://codespeak.net/pipermail/icalendar-dev/attachments/20110824/da60bcdc/attachment.key -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 945 bytes Desc: OpenPGP digital signature Url : http://codespeak.net/pipermail/icalendar-dev/attachments/20110824/da60bcdc/attachment.pgp From rok.garbas at gmail.com Wed Aug 24 23:42:07 2011 From: rok.garbas at gmail.com (Rok Garbas) Date: Wed, 24 Aug 2011 23:42:07 +0200 Subject: [icalendar-dev] Extracting private extension values in full form In-Reply-To: <4E5559F1.6090809@ieee.org> References: <4E5559F1.6090809@ieee.org> Message-ID: <4E55702F.1010506@gmail.com> On 24/08/11 22:07, Joe Sapp wrote: > On Wed 24 Aug 2011 02:56:47 PM EDT, Cori wrote: >> Hi, >> >> How would one go about extracting the non-standard properties (ie the X- named >> extensions) allowed by the iCalendar format? >> (non-standard properties: http://tools.ietf.org/html/rfc5545#section-3.8.8.2) > > Hi, > > I don't think icalendar supports RFC 5545 yet, just 2445. > See > http://codespeak.net/pipermail/icalendar-dev/2011-August/000181.html > for future plans. > Hey Cori, can you please put this into issue tracker -> https://github.com/collective/icalendar/issues can be done with some extra coding. i plan to support those properties for 3.x series which is going to be follow rfc5545. i'm planning to shut this list down. -- Rok Garbas - http://www.garbas.si -------------- next part -------------- A non-text attachment was scrubbed... Name: 0x9A8C3DC8.asc Type: application/pgp-keys Size: 3877 bytes Desc: not available Url : http://codespeak.net/pipermail/icalendar-dev/attachments/20110824/b4694f63/attachment.key -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 945 bytes Desc: OpenPGP digital signature Url : http://codespeak.net/pipermail/icalendar-dev/attachments/20110824/b4694f63/attachment.pgp