You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey,
I am working on a project which requires christian hollidays. A lot of those are relative to easter sunday.
python-dateutil already supports this extension to the RFC:
byeaster If given, it must be either an integer, or a sequence of integers, positive or negative. Each integer will define an offset from the Easter Sunday. Passing the offset 0 to byeaster will yield the Easter Sunday itself. This is an extension to the RFC specification.
I could try to implemet it myself, but I do not yet understand your code well enough to do this.
The text was updated successfully, but these errors were encountered:
Hello, thanks for the suggestion. When I did the port originally I was a bit reluctant to add non-standard extensions such as byeaster, since my intention was to be strict with RFC compliance. However maybe it's time to revisit this decision.
I will leave this ticket open for a bit to gauge if there are more people interested by this feature (please feel free to answer/react).
Hey, thanks for the response.
In my opinion this extension would not harm anybody: You can still parse every rfc conform rule and process it.
You will still generare conform rules, unless the user decides to use the "byeaster".
But to find this feature, he has to read some documentation (not just the rfc specs), which will state that the rule is not conform.
Hey,
I am working on a project which requires christian hollidays. A lot of those are relative to easter sunday.
python-dateutil already supports this extension to the RFC:
I could try to implemet it myself, but I do not yet understand your code well enough to do this.
The text was updated successfully, but these errors were encountered: