Open stardust85 opened 4 years ago
see also https://github.com/O365/python-o365/issues/457 :)
Greetings!
@stardust85 , on the contrary, sounds like a wise idea indeed. Thanks!
Let me first emphasize how this project started and was evolving so far:
And after a short review, it appears, the main differences with this project could be summarized like this:
SharePoint API is still treated as the first-class citizen since Microsoft Graph does not replace it
the ultimate goal to get model generated from metadata (what is called fluent API, the similar way how official Microsoft Graph SDKs are built)
Given all the the pros and cons and preferences, it feels there is more benefits for the community if those projects will continue evolve separated, what do you think?
p.s. would be glad to hear another opinions/ideas
Hi @vgrem nice to meet you! great library yours!
Greetings @janscas, likewise and congrats with achievement!
Hello @vgrem 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
what Office365-REST-Python-Client has better:
what python-o365 has better:
Would love to hear (read) your feedback on this!
P.S. Thanks a lot for all you've built here!