iCalendar

Software Screenshot:
iCalendar
Software Details:
Version: 3.8.4
Upload Date: 13 Apr 15
Developer: Rok Garbas
Distribution Type: Freeware
Downloads: 32

Rating: nan/5 (Total Votes: 0)

iCalendar is a widely used file format, mainly by calendar and personal agenda applications and websites.

This format can be used to store details about events, meetings, bookings, reservations and calendars.

iCalendar (.ics) files are used on a regular basis by applications and services like Google Calendar, Microsoft Outlook, Mozilla Thunderbird, Apple Calendar, and so on.

The iCalendar module allows developers to read .ics files and output their content to other applications and processing units.

The module can also generate iCalendar files on the fly, based on well-organized information fed to it.

The iCalendar module tries to stay as close as possible to the original iCalendar standard, as well as Python lets it do so.

Please refer to the documentation before delving into this project.

What is new in this release:

  • Added Python 3 support.

What is new in version 3.4:

  • Switch to unicode internally. This should fix all en/decoding errors.
  • Support for non-ascii parameter values.
  • Added functions to transform chars in string with '' + any of r',;:' chars into '%{:02X}' form to avoid splitting on chars escaped with ''.
  • Allow seconds in vUTCOffset properties.
  • Let Component.decode better handle vRecur and vDDDLists properties.
  • Don't let Component.add re-encode already encoded values. This simplifies the API, since there is no need explicitly pass encode=False.
  • Rename tzinfo_from_dt to tzid_from_dt, which is what it does.
  • More support for dateutil parsed tzinfo objects.

What is new in version 3.1:

  • Apply TZID parameter to datetimes parsed from RECURRENCE-ID
  • Localize datetimes for timezones to avoid DST transition errors.
  • Allow UTC-OFFSET property value data types in seconds, which follows RFC5545 specification.
  • Remove utctz and normalized_timezone methods to simplify the codebase. The methods were too tiny to be useful and just used at one place.
  • When using Component.add() to add icalendar properties, force a value conversion to UTC for CREATED, DTSTART and LAST-MODIFIED. The RFC expects UTC for those properties.
  • Removed last occurrences of old API (from_string).
  • Add 'recursive' argument to property_items() to switch recursive listing. For example when parsing a text/calendar text including multiple components (e.g. a VCALENDAR with 5 VEVENTs), the previous situation required us to look over all properties in VEVENTs even if we just want the properties under the VCALENDAR component (VERSION, PRODID, CALSCALE, METHOD).
  • All unit tests fixed.

What is new in version 3.0.1b2:

  • For all TZID parameters in DATE-TIME properties, use timezone identifiers (e.g. Europe/Vienna) instead of timezone names (e.g. CET), as required by RFC5545. Timezone names are used together with timezone identifiers in the Timezone components.
  • Timezone parsing, issues and test fixes.
  • Since we use pytz for timezones, also use UTC tzinfo object from the pytz library instead of own implementation.

Requirements:

  • Python 2.6 or higher
  • Pytz

Similar Software

Other Software of Developer Rok Garbas

unittest_jshint
unittest_jshint

14 Apr 15

github-collective
github-collective

20 Feb 15

Comments to iCalendar

Comments not found
Add Comment
Turn on images!