-
Notifications
You must be signed in to change notification settings - Fork 27.6k
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
[Bug]: issue with tokenizers #16445
Comments
+1, Gentoo linux, analog issue, installation step fail
|
I face the same issue while installing requirements :
|
This issue "shouldn't" happen if you are using python 3.10, the highest supported version for this project. As much as I wish we had a more up to date version of tokenizers and python compatible-- we don't. Perhaps this is caused because pypi does not have prebuilt binaries for that old of a version of tokenizers for that new of a version of python? Repost here if python 3.10.x doesn't fix it! |
nope |
same problem on ArchLinux |
fixed the tokenizer this one mental abuse me for over a week Commit hash: 82a973c |
This could be caused by incorrect rustc version? I have issue with toenizers as well on my Arch Linux, in my error log it hints I should compile it with rustc 1.74.0 or later, but I'm using 1.70, which is installed by rustup package. I'm trying to fix my own issue. |
could be but I think it more likely a bug on the tokenizer code that complie with older rust so in newer ver it just broke maybe |
I found out 1.65 work |
Getting the same problem on my M1 Mac. Tried downgrading to rust 1.65 and python 3.10.12
Any workarounds? |
some problem on my M2 Max Mac, I slove this question use conda create env use python 3.10.15. |
It looks original sources are already fixed (with So... is there a update of python libs? (I can't find what library uses this crate.) |
Stuck with the same issue |
M1 I think you need to have more packet btw that more likely a bug of ARM emulation |
no it just a really bug from python itself |
I'm using this condition:
I tried rustc 1.65.0, but it does not solve the problem. Finally, I rewrite
Thus, I think it is neither a bug of python or rustc. |
Sorry, also you need this patch, because of the update of transformer: |
Hit this issue when I accidentally used the wrong python version myself. you absolutely need to be on 3.10.6. if your build is failing due to unsafe rust code, then you likely are using the wrong python runtime. But the issue you're hitting is actually over here: Time continues to move forward. Libraries that the dependencies in requirements.txt depend on release new versions. Pip wanders into them. If you were using poetry instead of bare pip, then at least you could check in the lock file with the sum total of deps and their deps which would probably make for a more reproducible build. But when you mix and match major python versions, all bets are off. pyenv to the rescue. You know what? Running this out of a docker image would be pretty straight forward and might cut down on the finicky python env sensitivity. Just a thought. |
Checklist
What happened?
can't open because of the tokenizers can't build
Steps to reproduce the problem
idk
it just pop up
What should have happened?
it run as usual but now it bonked
What browsers do you use to access the UI ?
No response
Sysinfo
from my console can't open the webUI
Console logs
Additional information
No response
The text was updated successfully, but these errors were encountered: