-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Amount of nodes and edges have mistakes when reading adjlist file #6132
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! Thanks
networkx/readwrite/adjlist.py
Outdated
If spaces are embedded in the names of nodes, the parser in read_adjlist will | ||
be confused because space is the default delimiter. The parser will not | ||
know if a space belongs in the node name or is just a delimiter. | ||
To avoid this problem, specify an alternate delimiter when spaces are | ||
valid in node names. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If spaces are embedded in the names of nodes, the parser in read_adjlist will | |
be confused because space is the default delimiter. The parser will not | |
know if a space belongs in the node name or is just a delimiter. | |
To avoid this problem, specify an alternate delimiter when spaces are | |
valid in node names. | |
The default `delimiter=" "` will result in unexpected results if node names contain | |
whitespace characters. |
Just a minor wording suggestion - I think keeping this as short as possible would be best. Note also that the advice to specify an alternate delimiter may not be possible if the data was generated by someone other than the user.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay. I'll add that and correct it. Thank you @rossbar
@rossbar how about now? |
) * fixes #6036 * test load centrality * test dispersion * test dispersion * dispersion test * test dispersion * bug-fixes-for-issue-6088 * deleted * fixes for 5911 * bugfix for 5911
…tworkx#6132) * fixes networkx#6036 * test load centrality * test dispersion * test dispersion * dispersion test * test dispersion * bug-fixes-for-issue-6088 * deleted * fixes for 5911 * bugfix for 5911
…tworkx#6132) * fixes networkx#6036 * test load centrality * test dispersion * test dispersion * dispersion test * test dispersion * bug-fixes-for-issue-6088 * deleted * fixes for 5911 * bugfix for 5911
fixes #5911