Correctly parse a valid ISO 8601 datetime string.

At this stage, only datetime (or non-truncated date) formats are permitted.

Week number formats are not permitted in this version.

You can have an object in any of the following formats:

  • YYYY-MM-DDThh:mm
  • YYYY-MM-DDThh:mm:ss
  • YYYYMMDDThhmmss

Additionally, to support some legacy systems, in all cases the T can be replaced by a space. Essentially, this just combines the two representations, which is not strictly according to the specification, but is commonly used.

Also supported is using an hour of 24 to mean midnight at the end of the day: this is converted to the python object of the next day's 00:00:00. Using a non-zero minute/second/fraction will raise a ValueError.

A fractional value may be appended to the last component of a time part. Appending it elsewhere will raise a ValueError.

Finally, only naive datetime objects are supported at this time. Timezones may not be included in the format string.

Duration time formats of the following forms are also supported:

  • P1W2DT3H4M5S

Note that support for Year and Month data is not supported, as this does not make sense with python's timedelta object.

You may, as per ISO8601, drop fields that have no value.

Future (in no particular order):

  • Support timezones
  • Support durations fully
  • Support time intervals
  • Support repeating intervals
  • Support week-dates
  • Support truncated dates
  • Support time only objects (including truncated?)

The following references were used to determine supported formats:


0.2.3 - Added parse_date to module exports.

0.2.2 - Add methods for forcing return of a date (or time): parse_date()

0.2.1 - Initial support for duration data (excluding year/month).
  • Initial support for formatting objects.

0.1.6 - Allow for a date or datetime object to be passed to parse.

0.1.5 - Added support for fractional times.

0.1.1 - Helps if I spell my domain name right.

0.1 - Initial release.