fix extendability function name in bipartite.rst #7042
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dschult
added a commit
to BrunoBaldissera/networkx
that referenced
this pull request
Oct 23, 2023
Alex-Markham
pushed a commit
to Alex-Markham/networkx
that referenced
this pull request
Oct 26, 2023
Closed
jarrodmillman
pushed a commit
that referenced
this pull request
Oct 27, 2023
cvanelteren
pushed a commit
to cvanelteren/networkx
that referenced
this pull request
Apr 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
fix extendability function name in bipartite.rst
The name of the function maximal_extendability in the bipartite docs was not updated from
find_extendabilityduring PR review. So, the function doesn't show in current docs and creates quiet failures for documentation builds when looking forfind_extendbability.This might help e.g. #7040 successfully build the docs, but I am not sure. It should be fixed in any case.