RFC 5545 compatibility
Bug #890197 reported by
thet
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| dateutil |
Expired
|
Undecided
|
Unassigned | ||
Bug Description
python-dateutil implements RFC2445, but RFC5545 supersedes the former. While it's just a minor update, python-dateutil should support it.
A summary of all changes can be found here: http://
Revision history for this message
| Tomi Hukkalainen (tpievila) wrote | #1 |
| Changed in dateutil: | |
| status: | New → Incomplete |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in dateutil: | |
| status: | Incomplete → Expired |
To post a comment you must log in.
Dateutil uses iCalendar only with rrule, and didn't really require full compliance even before (for example rrule doesn't require the dtstart property, when fed a piece of iCalendar). What parts of RFC5545 should be supported, but are not?