milestone changed; keywords set

icmurray — Wed, 16 May 2012 09:09:28 GMT

keywords [0.5d] added
milestone changed from ckan-sprint-2012-05-15 to current-ckan-sprint-2012-05-29

icmurray — Thu, 24 May 2012 15:21:56 GMT

This helper function won't parse UTC offset if passed a UTC offset as "+01:00"; but incorrectly parses the UTC offset "+0100" as 100 microseconds.

Resolution:

I've decided to keep the behaviour of not parsing UTC offsets because we currently don't store timezone information in the database; and I think that either dropping the tzinfo, or adjusting for it would appear to be "magic behaviour" from the user's perspective. Also, as this is a helper function, I think it makes sense to keep the behaviour as is, even if it's slightly non-standard.

This fix [1] maintains all the old non-ISO behaviour:

But won't parse "+0100" as microsecond precision.

I tried using a couple of python modules for parsing date strings; but none maintained the same behaviour.

status changed; resolution set

icmurray — Mon, 28 May 2012 09:23:44 GMT