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
this might seem weird, but I think those two should be different:
>>> import parsedatetime; "{}".format(parsedatetime.Calendar().parseDT("next tuesday 18:00", tzinfo=pytz.timezone("CET"))[0]) '2022-03-29 18:00:00+02:00' >>> import parsedatetime; "{}".format(parsedatetime.Calendar().parseDT("next tuesday 18:00 UTC", tzinfo=pytz.timezone("CET"))[0]) '2022-03-29 18:00:00+02:00' >>>
ie. if I specifically pass a timezone in my date string, shouldn't parsedetime at least try to parse that timestamp?
this also fails with more regular date formats:
>>> import parsedatetime; "{}".format(parsedatetime.Calendar().parseDT("2022-03-03 18:00 UTC", tzinfo=pytz.timezone("CET"))[0]) '2022-03-03 18:00:00+01:00' >>> import parsedatetime; "{}".format(parsedatetime.Calendar().parseDT("2022-03-03 18:00 UTC", tzinfo=pytz.timezone("EST"))[0]) '2022-03-03 18:00:00-05:00' >>>
The text was updated successfully, but these errors were encountered:
No branches or pull requests
this might seem weird, but I think those two should be different:
ie. if I specifically pass a timezone in my date string, shouldn't parsedetime at least try to parse that timestamp?
this also fails with more regular date formats:
The text was updated successfully, but these errors were encountered: