Joining forces with https://github.com/vgrem/Office365-REST-Python-Client

[stardust85]

Hello @janscas et al. I know this is very crazy idea, but still I feel a need to tell you about it :) These two projects look so similar to me that I think the whole python MS365 community would gain from merging these two together.

My idea is to help project A to reach feature parity with project B (so all features from B are also in A) and then to deprecate project B in favor of project A.

Now the question is which of these two should be A and which should be B. Maybe the comparison below will help:

projects comparison

python lines of code measured by cloc tool on master branches

• Office365-REST-Python-Client: 3987 lines (5492 lines including tests and examples)
• python-o365: 8274 lines (8901 lines including tests and examples)

what Office365-REST-Python-Client has better:

• has much more tests and what's more important, experience with them and drive to write them
• less flake8 errors

what python-o365 has better:

• error handling and smoother API (e.g. https://github.com/vgrem/Office365-REST-Python-Client/issues/197)
• more features? (just guessing based on code size, using only sharepoint part of the library...)

Would love to hear (read) your feedback on this!

P.S. Thanks a lot for all you've built here!

[stardust85]

see also https://github.com/vgrem/Office365-REST-Python-Client/issues/198 :)

[alejcas]

Hi @stardust85 I'm open to new developments and merging or whatever, but I think the two libraries use different apis, and although O365 is capable of working with other apis (for example I'm writing a connection to PowerBI Rest apis with O365), for the moment it's outside of the scope of the project to develop with another apis. Now just works for Outlook rest apis and MS Graph.

Also nowadays I don't have the time to work on this so expect little time implication for me and I feel this supposed merging will require a lot of work.