parse_datetime can't parse datetimes returned from postgresql

[no]

The datetime format returned by postgresql is "2014-06-11 23:31:38.134266+00" which is failed to parsed because the offset is only two digits.

[Aymeric Augustin]

Where does Django call parse_datetime on a value returned by PostgreSQL?

If it never does, I'd just document the expected format.

[no]

django.db.models.fields.DateTimeField calls it in its to_python method. I recommend django switch to be closer to ISO-8601 which allows the following formats: Z; [+-]hh:mm, [+-]hhmm, [+-]hh
Currently parse_datetime allows all except the last case which was taken out in 2f59e94a4150c84c8b4 because it (mistakenly) also allowed [+-]hm

I propose that [+-]hh be reintroduced with the semantics outlined in ISO-8601. (I'll create a PR)

[Aymeric Augustin]

Wikipedia confirms that ±hh is supported. Let's do this.

[no]

​https://github.com/django/django/pull/2804

[Aymeric Augustin]

Looks good. My only comment is the most insignificant I ever left on a PR :-) If you can amend the commit and force-push it, I'll merge it.

[no]

Done, and flake8 passes on both changed files.

[Richard Eames <reames@…>]

In 7beaeeed2b99ec120486ee53e1eb7f1fe2515b9c:

Fixed #22814 -- Allowed ISO-8601 [+-]hh timezone format in parse_datetime

[Aymeric Augustin <aymeric.augustin@…>]

In 26cd19561331ac4a8a5f084a30c8ba0123d33278:

Merge pull request #2804 from AsymmetricVentures/issue22814

Fixed #22814 -- Allowed ISO-8601 [+-]hh timezone format in parse_datetime

[anonymous]

Any chance of getting this backported to 1.7 and/or 1.6?

[Aymeric Augustin]

I'll do it for 1.7.

I'd rather not do it in 1.6. I'm wary of making small changes in low level utilities in stable versions because people tend to rely on the exact behaviour, sometimes after checking the source.

[Aymeric Augustin <aymeric.augustin@…>]

In 8dcc7810f07e2ce76ebee50c70a5c16f1bc9edec:

[1.7.x] Fixed #22814 -- Allowed ISO-8601 [+-]hh timezone format in parse_datetime

Backport of 7beaeeed from master.