[MRG] fix: make the documentation of _get_loss_unbalanced as a raw string #716
Conversation
This file contains hidden or 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
This is to avoid the following warning: SyntaxWarning: invalid escape sequence '\m'
framunoz
changed the title
framunoz
changed the title
* fix: add backslash to fix the error in the documentation * refactor: delete space * Update RELEASES.md --------- Co-authored-by: Francisco Muñoz <fmunoz@ug.uchile.cl>
Contributor
Author
|
@rflamary the PR should be ready to be merge. This PR fixes a small warning introduced by a bug in the documentation of the latest version of POT. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This is to avoid the following warning:
Types of changes
Add a
rat the beggining of the_get_loss_unbalanceddocumentationMotivation and context / Related issue
When I update the library, I realised that throws the following warning:
How has this been tested (if it applies)
PR checklist