New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tweak sequence tokenization #10904
Tweak sequence tokenization #10904
Conversation
Unit Test ResultsSee test report for an extended history of previous test failures. This is useful for diagnosing flaky tests. 15 files ± 0 15 suites ±0 3h 13m 3s ⏱️ - 6m 13s Results for commit 097a48a. ± Comparison against base commit f51fa77. This pull request removes 1 and adds 2 tests. Note that renamed tests count towards both.
|
seen = _seen.get() | ||
tok = None | ||
except LookupError: | ||
# This is for debug only, for when normalize_token is called outside of |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems odd, do we really want to keep this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is extremely useful to figure out why tokens have changed when anything goes wrong. I'm already using it in dask/distributed#8185
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
k
thx |
Allow calling normalize_token() outside of tokenize(). This is useful for debugging purposes.
Additionally, polish some tests in test_tokenize.