On Dec 7, 2017, at 7:52 PM, Mike Miller firstname.lastname@example.org wrote:
Guess the argument for limiting what it accepts would be that every funky variation will need to be supported until the endtimes, even those of little use or utility.
I suppose so, but not that hard once implemented and tests in place.
How about this for a “practicality beats purity” approach:
.fromiso() will parse the most commonly used iso8601 compliant date time strings.
It is guaranteed to properly parse the output of .isoformat()
It is Not a validator — it may except non-iso compliant strings, and may give surprising results when passed such. <end/>
In any case, I sure hope it will accept iso strings both with and without the “T”.
But again: Paul, do whatever you think is best.
On the other hand, it might be good to keep the two implementations the same for consistency reasons.
Thanks either way, -Mike
On 2017-12-07 17:57, Chris Barker - NOAA Federal wrote: _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/chris.barker%40noaa.gov