Fix spaces in BPE decoding, Python 3.8 compatibility #373
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
pierotofy
changed the title
|
I've also mistakenly broke Python 3.8 compatibility (ugh! so sorry about that). I'm still amazed that Python devs are OK with language breaking features between minor versions ( |
Good catch thanks. I guess type annotations are a new feature so it's not consistently available in Python 3. |
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.
I've made a mistake in the BPE decoding. ["Tok@@", "en"] should be decoded "Token", not "Tok en".
I've found this while converting/testing some BPE models from OPUS.