ValueError: RRULE UNTIL values must be specified in UTC when DTSTART is timezone-aware
I've been trying to parse recurrence rules using python's dateutil rrule package
However, I am getting an odd error inconsistent with the way I understand recurrence rules
The error is
ValueError: RRULE UNTIL values must be specified in UTC when DTSTART is timezone-aware
The function I'm calling is
recurrence = "RRULE:FREQ=WEEKLY;UNTIL=20181206T075959Z;BYDAY=MO,WE,FR"
rule = rrulestr(recurrence, dtstart=datetime.now())
If the until is structured as UNTIL=20181206T075959Z
, isn't that in UTC? Why would this error show up, and what is an appropriate solution? The thing is, this works with
"RRULE:FREQ=WEEKLY;UNTIL=20191206T075959;BYDAY=MO,WE,FR"
, which I thought was not in UTC, because it was missing the 'Z'
python python-dateutil rrule
add a comment |
I've been trying to parse recurrence rules using python's dateutil rrule package
However, I am getting an odd error inconsistent with the way I understand recurrence rules
The error is
ValueError: RRULE UNTIL values must be specified in UTC when DTSTART is timezone-aware
The function I'm calling is
recurrence = "RRULE:FREQ=WEEKLY;UNTIL=20181206T075959Z;BYDAY=MO,WE,FR"
rule = rrulestr(recurrence, dtstart=datetime.now())
If the until is structured as UNTIL=20181206T075959Z
, isn't that in UTC? Why would this error show up, and what is an appropriate solution? The thing is, this works with
"RRULE:FREQ=WEEKLY;UNTIL=20191206T075959;BYDAY=MO,WE,FR"
, which I thought was not in UTC, because it was missing the 'Z'
python python-dateutil rrule
add a comment |
I've been trying to parse recurrence rules using python's dateutil rrule package
However, I am getting an odd error inconsistent with the way I understand recurrence rules
The error is
ValueError: RRULE UNTIL values must be specified in UTC when DTSTART is timezone-aware
The function I'm calling is
recurrence = "RRULE:FREQ=WEEKLY;UNTIL=20181206T075959Z;BYDAY=MO,WE,FR"
rule = rrulestr(recurrence, dtstart=datetime.now())
If the until is structured as UNTIL=20181206T075959Z
, isn't that in UTC? Why would this error show up, and what is an appropriate solution? The thing is, this works with
"RRULE:FREQ=WEEKLY;UNTIL=20191206T075959;BYDAY=MO,WE,FR"
, which I thought was not in UTC, because it was missing the 'Z'
python python-dateutil rrule
I've been trying to parse recurrence rules using python's dateutil rrule package
However, I am getting an odd error inconsistent with the way I understand recurrence rules
The error is
ValueError: RRULE UNTIL values must be specified in UTC when DTSTART is timezone-aware
The function I'm calling is
recurrence = "RRULE:FREQ=WEEKLY;UNTIL=20181206T075959Z;BYDAY=MO,WE,FR"
rule = rrulestr(recurrence, dtstart=datetime.now())
If the until is structured as UNTIL=20181206T075959Z
, isn't that in UTC? Why would this error show up, and what is an appropriate solution? The thing is, this works with
"RRULE:FREQ=WEEKLY;UNTIL=20191206T075959;BYDAY=MO,WE,FR"
, which I thought was not in UTC, because it was missing the 'Z'
python python-dateutil rrule
python python-dateutil rrule
asked Jan 1 at 16:37
JohnDoeJohnDoe
666622
666622
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
This may be a confusing error message because it is taken from the RFC spec but doesn't really explain the context.
The problem is that dtstart
and UNTIL
must both either be naive or timezone-aware, and the spec actually specifies that UNTIL
has to be UTC specifically in that case.
To fix your code, you can just make dtstart
timezone-aware:
from dateutil.tz import UTC
recurrence = "RRULE:FREQ=WEEKLY;UNTIL=20181206T075959Z;BYDAY=MO,WE,FR"
rule = rrulestr(recurrence, dtstart=datetime.now(UTC))
Feel free to report the confusing error message on dateutil's issue tracker.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53997143%2fvalueerror-rrule-until-values-must-be-specified-in-utc-when-dtstart-is-timezone%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
This may be a confusing error message because it is taken from the RFC spec but doesn't really explain the context.
The problem is that dtstart
and UNTIL
must both either be naive or timezone-aware, and the spec actually specifies that UNTIL
has to be UTC specifically in that case.
To fix your code, you can just make dtstart
timezone-aware:
from dateutil.tz import UTC
recurrence = "RRULE:FREQ=WEEKLY;UNTIL=20181206T075959Z;BYDAY=MO,WE,FR"
rule = rrulestr(recurrence, dtstart=datetime.now(UTC))
Feel free to report the confusing error message on dateutil's issue tracker.
add a comment |
This may be a confusing error message because it is taken from the RFC spec but doesn't really explain the context.
The problem is that dtstart
and UNTIL
must both either be naive or timezone-aware, and the spec actually specifies that UNTIL
has to be UTC specifically in that case.
To fix your code, you can just make dtstart
timezone-aware:
from dateutil.tz import UTC
recurrence = "RRULE:FREQ=WEEKLY;UNTIL=20181206T075959Z;BYDAY=MO,WE,FR"
rule = rrulestr(recurrence, dtstart=datetime.now(UTC))
Feel free to report the confusing error message on dateutil's issue tracker.
add a comment |
This may be a confusing error message because it is taken from the RFC spec but doesn't really explain the context.
The problem is that dtstart
and UNTIL
must both either be naive or timezone-aware, and the spec actually specifies that UNTIL
has to be UTC specifically in that case.
To fix your code, you can just make dtstart
timezone-aware:
from dateutil.tz import UTC
recurrence = "RRULE:FREQ=WEEKLY;UNTIL=20181206T075959Z;BYDAY=MO,WE,FR"
rule = rrulestr(recurrence, dtstart=datetime.now(UTC))
Feel free to report the confusing error message on dateutil's issue tracker.
This may be a confusing error message because it is taken from the RFC spec but doesn't really explain the context.
The problem is that dtstart
and UNTIL
must both either be naive or timezone-aware, and the spec actually specifies that UNTIL
has to be UTC specifically in that case.
To fix your code, you can just make dtstart
timezone-aware:
from dateutil.tz import UTC
recurrence = "RRULE:FREQ=WEEKLY;UNTIL=20181206T075959Z;BYDAY=MO,WE,FR"
rule = rrulestr(recurrence, dtstart=datetime.now(UTC))
Feel free to report the confusing error message on dateutil's issue tracker.
answered Jan 1 at 17:00
PaulPaul
5,30453166
5,30453166
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53997143%2fvalueerror-rrule-until-values-must-be-specified-in-utc-when-dtstart-is-timezone%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown