-
-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EXDATE support not working properly #20
Comments
@wichmannpas Thanks for reporting this. I see the following workflow:
You and anyone is very welcome to take on these tasks. I will not do it today, rather when I like to go into a nice development flow. |
This is the test result:
It seems, the date of the recurring event is automatically transformed into a time zone. This leads to the exdate not matching. Compare:
@wichmannpas, I can confirm the behavior is a bug. |
A this point I wonder if this is a bug in this module. It could very well be that
I will check with the specification. Since Exdates can only be dates, I see no problem with adding the special behavior of EXDATES differing in time zone. Note for implementation:
I should contact Davx5 and see if this is intentional or not. |
Posted: https://forums.bitfire.at/topic/2234/differences-in-exdate-calculations-how-to-achieve-compatibility It seems their interpretation is broader but very well in scope of the specification. From my intuition, I would say, this library needs to be changed. Possible places:
|
This should now be fixed by #25 |
This fix is included in v0.1.14b |
Thanks for your work and for fixing this! I am currently having rather tight time constraints, so I was not yet able to look into this myself.
|
The
EXDATE
support (from the most recent PyPi version) does not seem to be working properly.I have for example an event like the following where at least some of the EXDATE values are not honoured:
The text was updated successfully, but these errors were encountered: