Except that arrow is simple-minded when trying to parse date strings (compared to dateparser or delorean[1]). By default, it only tries to match a few patterns.

Except that arrow is simple-minded when trying to parse date strings (compared to dateparser or delorean[1]). By default, it only tries to match a few patterns. You'll see a lot of this: arrow.parser.ParserError: Could not match input to any of ['YYYY-MM-DD', 'YYYY-MM', 'YYYY'] on '01-06-17' Here's a list of (US English–centric) test dates that dateparser ((ddp.get_date_data(date)['date_obj']).date()) and delorean (delorean.parse(date, dayfirst=False, yearfirst=False).date) both parse correctly, nearly all of which arrow fails on: 01-06-2017 01-06-17 2017-01-06 01/06/2017 01/06/17 2017/01/06 Jan 6, 2017 Jan 6 2017 2017, Jan 6 2017 Jan 6 2017, January 6 2017 January 6 January 6, 2017 January 6 2017 January 6nd, 2017 January 6rd, 2017 January 6st, 2017 January 6th, 2017 January 6nd 2017 January 6rd 2017 January 6st 2017 January 6th 2017 2017, January 6nd 2017, January 6rd 2017, January 6st 2017, January 6th 2017 January 6nd 2017 January 6rd 2017 January 6st 2017 January 6th 01//06/2017 01//06//2017 01--06-2017 01--06--2017 01/06-2017 01-06/2017 I like Delorean's API better than arrow's (strictly personal preference) but think dateparser's language detection is interesting. [1] http://delorean.readthedocs.org/en/latest/quickstart.html http://delorean.readthedocs.org/en/latest/quickstart.html