dateutil VS arrow

Here is an example for a single cell (I'm using the dateutil package to parse the strings):

The parser module gives direct access to parser.ParserError, which could be accessed by way of parser.ParserError.

[1] https://github.com/dateutil/dateutil

pdbpp: Improved pdb boltons: assorted python addtions twisted: event driven networking framework sorcery: Dark magic in python, things know where+how they are being called, helps reducing boilerplate sh: Better alternative for subprocess module, much more pythonic taskipy: npm run scipt_name like functionality snoop: pdb lite, record+replay function steps birdseye: graphical debugger remote-pdb: easy pdb from inside containers typer: wrapper around click for simpler code for CLIs arrow: Always TZ aware datetimes, plus more features more-itertools: more functions for iterators pydantic: data validation + dataclasses loguru: better logging notifiers: sending notifications from python

Arrow makes dealing with dates and timezones way easier than the built-ins. Years ago I got sick of looking up how to use date types properly for the umpteenth time and found arrow, and now use it all the time.

Arrow v1.0: After 8 years, even better dates and times for Python\ (59 comments)

You can also take a look at the parsing formats that Arrow tries to parse: https://github.com/arrow-py/arrow/blob/master/arrow/parser.py#L215