DEP : adding not_implemented_for("multigraph”)
to k_core
, k_shell
, k_crust
and k_corona
#7121
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the first commit, I have deprecated the behavior of the above four
k_
functions to not take aMultiGraph
object as an argument.The above four functions are not defined for a multigraph so it would be appropriate to add a
not_implemented_for("multigraph”)
decorator and strictly not allow aMultiGraph
object to avoid any confusion about multigraph andMultiGraph
class.Also, when the
core_number
dictionary is not passed as an argument in these functions and aMultiGraph
object is passed, then aNetworkXNotImplemented
exception is raised. But, when thecore_number
dictionary is given then the sameMultiGraph
graph won't raise any exceptions. So, to avoid this kind of inconsistent behavior we should add the decorator.In the second commit, I have just added some more tests for the other functions in
core.py
.origin : #7027
Thank you :)