-
Notifications
You must be signed in to change notification settings - Fork 28.2k
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
Dependency version check fails for tokenizers #11107
Comments
Thank you for this report, @guyrosin Any idea how we could reproduce this problem? This works for me:
I do see a different problem though. I see we now have: I didn't expect a range definition, when I wrote this code, so currently it tries to do:
which is wrong - I'm surprised Actually does the problem go away if you edit Also if you could add a debug print and see what's in Thanks. |
Could you please give a try to this PR: #11110 and let me know if the problem goes away? Thank you. |
Thanks for the fast response @stas00! I'm glad this helped you find another bug :) I guess the problem in my case is with the tokenizers distribution. I'm getting:
Even after reinstalling Edit: to make it clear: using
|
Does it help if you update/explicitly install this library:
and then retry? It's good to know that But sometimes the Does it make any difference if you first uninstall What if you create a new environment and try there? |
OK, it seems like my environment was corrupted indeed - there was a |
Yay! Glad it worked, @guyrosin! |
Environment info
transformers
version: 4.5.0tokenizers
version: 0.10.2 (checked also 0.10.1)Who can help
@stas00, @sgugger
Information
When importing
transformers
, the new dependency version check code (#11061) seems to fail for the tokenizers library:importlib.metadata.version('tokenizers')
returns None instead of the version string.The problem arises when using:
To reproduce
Steps to reproduce the behavior:
import transformers
The root problem is this:
Expected behavior
importlib.metadata.version('tokenizers')
should return its version string.The text was updated successfully, but these errors were encountered: