python-o365 VS arrow

Shout out to python-o365 and circuit-maintenance-parser. Narrow scopes but solve some difficult problems.

Made the switch from basic auth to oauth2 using an app registration in azure today. we cannot get our script working properly with this python 365 module - https://github.com/O365/python-o365

Are you using Office 365 Exchange for your mail provider by chance? It's possible your administrator has prevented access from the mail server without proper authentication. If that's the case then what I would suggest is having your admin register your app in azure, then you'd use that rather than trying to authenticate directly with the mail server itself. Here's a library that works well for that setup: https://github.com/O365/python-o365

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