Niko Fink
Niko Fink
The additions of `event-cmp.rst` and `timezone.rst` were mostly me trying to document for myself (and in the same way provide some basic tests for) some more complicated functionality. These should...
Jep, please work on 0.8 i.e. the state of the `main` branch. 0.7 on the [`version-0.7` branch](https://github.com/ics-py/ics-py/tree/version-0.7) is vastly different and shouldn't receive too much attention anymore.
Some further possible ideas - filtering events based on their attributes, e.g. their category - adding / updating / removing attributes, e.g. setting the category or dropping all private information...
```python for event in calendar.events: if "Party" in event.name: print("🎉", event) ``` The answer to your second question is in the API docs: [Timeline.on](https://icspy.readthedocs.io/en/stable/api.html#ics.timeline.Timeline.on) PS: using a discussion would be...
> As I said bellow, I just came across the fact that we would need X-WR-CALNAME for practical reason. I guess the best way to support this would be parsing...
If you remove the added `CalendarNameConverter` by reverting the changes to `src/ics/converter/types/calendar.py` that should be it. Then we simply add the name field and letting its Converter be autogenerated without...
Should be fixed once we release [v0.7.1](https://github.com/ics-py/ics-py/tree/version-0.7) which contains the parsing speed fixes, see #318. Alternatively, you can try upgrading directly to v0.8 which contains a *lot* more goodies, but...
Probably pretty quickly once #318 is resolved. But I would really recommend upgrading to 0.8. It switches back to using Python's builtin `datetime` because `arrow` is, amongst other things, unable...
That is an issue with the customizability of (de)serializiation which I hope to fix before the v0.8 release. Could you try the following (which is borrowed from what is done...
If it's just `Event.begin` and `end` that's problematic for you, you could also fix that in a custom subclass that automatically (un-)wraps the arrow/built-in datetime objects. But please be aware...