fix small mistake in BQFClassGroupQuotientMorphism documentation #37233
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
|
Documentation preview for this PR (built with commit 07bb20a; changes) is ready! 🎉 |
vbraun
pushed a commit
to vbraun/sage
that referenced
this pull request
Feb 7, 2024
…documentation
The possibility to pass discriminants to the constructor instead of
`BQFClassGroup` objects was present for an earlier version of sagemath#37074,
but it was removed during review. However, it seems I forgot to update
the docstring accordingly.
URL: sagemath#37233
Reported by: Lorenz Panny
Reviewer(s): Travis Scrimshaw
yyyyx4
deleted the
public/fix_small_mistake_in_BQFClassGroupQuotientMorphism_documentation
branch
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.
The possibility to pass discriminants to the constructor instead of
BQFClassGroupobjects was present for an earlier version of #37074, but it was removed during review. However, it seems I forgot to update the docstring accordingly.