-
Notifications
You must be signed in to change notification settings - Fork 29
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
Error: 'bytes' object has no attribute 'suffix'. on xkalamine install #163
Comments
Strange, I can’t reproduce this error here (with Ubuntu 22.04). Could you please :
|
This is the whole output after the prompt:
It appears to be an issue with the parser, not Kalamine. Since creating the issue, I downgraded Kalamine to 0.13 and it works. I attach the layout file (it has .txt suffix since GitHub does not let me to attach a .toml file. |
How did you install kalamine? The recommend method is using pipx. See the README, which isolate dependencies. If not, give it a try after deinstalling your previous installation of kalamine. What Python version are you using? The python --version |
I agree the
This is weird : if the parser didn’t work, then I’m tempted to think this might be something related to This won’t install your layout, but as
Oh, I didn’t know that. The Python2 trick would surprise me a bit, as all #!/usr/bin/env python3 However, I did drop those Python3 shebangs in non-script modules in #105. If that’s related, then version 0.22 should work and version 0.33 should not. |
I can confirm the issue on a new machine. Downgrading kalamine to 0.22 fixed it. |
I have upgraded to kalamine v0.36.
I used the 1dk keyboard layouts before without an issue.
Now I build my own layout, but when trying to install it using the
sudo env "PATH=$PATH" xkalamine install <path/to/layout>.toml
I get the following cryptic error
File could not be parsed.
Error: 'bytes' object has no attribute 'suffix'.
The .toml file is valid. I can use xkalamine apply to use it ad-hoc and I can test the layout using kalamine watch.
I am on Ubuntu 20.04 LTS.
The text was updated successfully, but these errors were encountered: