dateutil/dateutil

Add in RFC7529 extensions to rrule.

Open

#285 opened on Jul 25, 2016

View on GitHub
 (3 comments) (6 reactions) (0 assignees)Python (2,189 stars) (470 forks)batch import
enhancementhelp wantedmedium-difficultyrrule

Description

Looks like RFC7529 provides some significant extensions to the RRULE, including a more satisfactory resolution to #149.

We should probably implement these extensions. I haven't read it thoroughly, but we may want to see if these extensions allow BYEASTER to be easily recast as a combination of other rules. This will allow us to generate compliant rrulestr strings specified with the byeaster input.

It also seems like our implementation is based on RFC2445, which is obsoleted by RFC5545. We should update rrule as appropriate for both.

Contributor guide

Tech stack
python
Domain
backend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Pythondateutil libraryRFC 5545RFC 7529
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
Start by reading RFC7529 and RFC5545 to understand the extensions and changes required. Then examine the current rrule implementation in dateutil/rrule.py, especially how BYEASTER is handled (see issue #149). Assess how the new RSCALE and other extensions from RFC7529 can be integrated. Finally, propose a detailed implementation plan in the issue before coding.