-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
API: distinction between libpysal and networkx graphs #579
Comments
Some initial ideas:
|
what about leaving "graph" and using |
I was thinking something like that, but then thought it would be counterproductive in our general efforts to move away from the "weights" terminology on the PySAL side of things. |
Are we trying to move away from weights terminology or just weights class? |
neighbors_graph ? |
I guess I am not sure. I thought so, but maybe I misinterpreted. Perhaps we can get other devs' opinions on that?
As for that, I think it works well. We could even truncate it we wanted: |
Let's pick it up during the next PySAL dev meeting. |
We have decided to keep the name |
We currently use both libpysal and nx graphs, and unfortunately use the term
graph
for both. Compare this:momepy/momepy/graph.py
Line 67 in 889fb44
and this
momepy/momepy/functional/_distribution.py
Line 105 in 889fb44
I don't think it is wise to do that. And since the contents of the
graph.py
module will likely not change signficantly, we should probably use better name within the new functional module for libpysal graphs to avoid confusion.The text was updated successfully, but these errors were encountered: