datetime: Read in isoformat() output

[perey]

BPO	19004
Superseder	bpo-15873: datetime: add ability to parse RFC 3339 dates and times

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2013-09-11.11:32:41.788>
created_at = <Date 2013-09-11.10:20:13.794>
labels = ['type-feature', 'library']
title = 'datetime: Read in isoformat() output'
updated_at = <Date 2013-09-11.11:32:41.787>
user = 'https://bugs.python.org/perey'

bugs.python.org fields:

activity = <Date 2013-09-11.11:32:41.787>
actor = 'r.david.murray'
assignee = 'none'
closed = True
closed_date = <Date 2013-09-11.11:32:41.788>
closer = 'r.david.murray'
components = ['Library (Lib)']
creation = <Date 2013-09-11.10:20:13.794>
creator = 'perey'
dependencies = []
files = []
hgrepos = []
issue_num = 19004
keywords = []
message_count = 1.0
messages = ['197482']
nosy_count = 1.0
nosy_names = ['perey']
pr_nums = []
priority = 'normal'
resolution = 'duplicate'
stage = 'resolved'
status = 'closed'
superseder = '15873'
type = 'enhancement'
url = 'https://bugs.python.org/issue19004'
versions = ['Python 3.4']

[perey]

At present, the datetime module does not provide the capability to parse its own output from the isoformat() methods.

strptime() can't handle timezones with colons in them (and anyway it seems to me you'd need to try several possible format strings depending on ' ' vs 'T' separators, presence/absence of microseconds, pres/abs timezone...). Adding this capability would be one option (%f already establishes a precedent for adding codes outside of what C supports).

Another, perhaps superior option would be a specific method for parsing the output of isoformat().