Author: junboli <junbo85...@gmail.com>
Date: Fri Jan 19 18:53:21 2018 +0800
Handle TZ change in iso8601 >=0.1.12
The iso8601 lib introduced a change such that if running on
python 3.2 or later it internally uses the python timezone
information instead of its own implementation.
This does not change direct date handling, but when converting
this value there is a slight difference where now python 2.x
will show UTC times as "UTC", but on python 3 they will end up
The to_primitive call for DateTime fields was doing an exact match
on "UTC" to determine whether to include "Z" in the resulting string.
This updates that handling to recognize either of the new values.
** Changed in: manila
Status: In Progress => Fix Released
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Change in iso8601 0.1.12 date format breaks parsing with py35
Status in Cinder:
Status in Glance:
Status in OpenStack Identity (keystone):
Status in Manila:
Status in OpenStack Compute (nova):
Status in oslo.utils:
Status in oslo.versionedobjects:
New package of iso8601 returns string in the format:
This is resulting in date string comparison failures and
timeutils.parse_isotime errors with:
ValueError: Unable to parse date string '2014-08-08T00:00:00UTC+00:00'
To manage notifications about this bug go to:
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : firstname.lastname@example.org
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp