We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When parsing a vevent using a custom time zone (see #173), error messages like this, which - sorry to say - are no use:
ERROR:root:'(UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna'
In the error message I'd like to learn
I tracked this message down to https://github.com/eventable/vobject/blob/0.9.6.1/vobject/icalendar.py#L83. At this point there is no chance to know the file or the item, not even the item-element. Anyhow, the message should at least read
ERROR:root:Unknown Timezone: '(UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna'
import vobject # for reproducing of thus bug, this stipped down vevent is enough VEVENT = """ BEGIN:VCALENDAR VERSION:2.0 BEGIN:VEVENT UID:1-2-3-4 DTSTART;TZID="(UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna" :20200504T110000 DTEND;TZID="(UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna":2 0200504T113000 DTSTAMP:20200303T123456Z SUMMARY:Some Appointment END:VEVENT END:VCALENDAR """ obj = tuple(vobject.readComponents(VEVENT))[0] obj.prettyPrint()
The text was updated successfully, but these errors were encountered:
Improve log message for unknown timezone
84cf7d1
Closes skarim#174.
Successfully merging a pull request may close this issue.
When parsing a vevent using a custom time zone (see #173), error messages like this, which - sorry to say - are no use:
Expected result
In the error message I'd like to learn
I tracked this message down to https://github.com/eventable/vobject/blob/0.9.6.1/vobject/icalendar.py#L83. At this point there is no chance to know the file or the item, not even the item-element. Anyhow, the message should at least read
How to reproduce
The text was updated successfully, but these errors were encountered: