Dan Schult

My one-two line summary is that it allows us to change the order of keyword arguments and it makes the user code more readable while reducing silent hidden bugs. We...

Thanks for this set of contributions (which keeps on coming :). It is growing quite long and that makes review more difficult. Let's make any further additions as separate PRs...

I'd welcome a move toward using keyword-only and position-only restrictions now available in python3. Issue #4100 addresses that. Meanwhile, the problem pointed out here is still a problem -- reversing...

Ha Haa.... Yes, this is an oldie. The history is that it was originally part of networkx, but in the early days we decided it shouldn't be part of the...

Thanks @erelsgl Can you "resolve" the comments/requests for changes you made? @danigil this is a little unusual because there has already been so much back and forth here in this...

You should push any additional changes to your branch on your github repo (the fork you made of the networkx repo). Any push to that branch is automatically picked up...

@erelsgl can you go through the documentation for this PR and make sure the definitions and statements of things that are proven are correct and precise? Also, just like writing...

Yes, let's put the envy-free matching code into a separate module with that name. That'll help with the documentation. Thanks!

Thanks for the report. I'm not sure how to make this work. I suspect it is related to the fact that the arrows are patches, while the non-arrows are a...

This info was quite helpful for me -- thank you! I have an idea for how it could work within `nx.draw_networkx_edges`, but I'm not sure it will work. I discovered:...