-
Notifications
You must be signed in to change notification settings - Fork 106
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
cannot import name 'Checker' from 'shaperglot' [googlefonts.glyphsets.shape_languages] #4987
Comments
on the legacy_checkids.py file. (issue fonttools#4987)
Indeed there is a typo. But I am not sure that's related to the issue you're reporting. I agree that this check should not run on Adobe Fonts profile, and it is not listed there. So maybe there's something else on your setup referencing that check. |
on the legacy_checkids.py file. (issue #4987)
Please try to run fontbakery from git which now includes a fix for that typo and let me know if your problem persists. |
You shouldn't use dots in the check-id. Use forward-slashes instead. |
Also, please inspect your setup looking for any fontbakery config file or custom invocation that may be referencing that shape_languages check (either using its old ID or the current one). |
Running into a related issue (also
Fortunately, this doesn’t seem to affect further progress. |
Hey @felipesanches, thanks so much for taking a look! I deactivated completely removed the old vent, then updated pip and did a fresh install of the latest dev version of Font Bakery:
But I seem to be having the same problem:
I also tried a couple of variations on the check name, with similar results:
|
Where might such configuration exist? Outside of fontbakery config files or custom profiles (neither of which I’m calling here) I don’t know where to look. |
I'd look at the imports in |
The problem here is that you have the latest released version of shaperglot installed, and Fontbakery is relying on the new API of the 1.0 prerelease. It's pretty helpful for me to know that Fontbakery works with the new API, and I should just hurry up and release 1.0, but relying on an prerelease version which is harder for users to install is unfortunate. The fix here is |
Observed behaviour
I’m trying to run the adobe fonts profile.
It mostly seems to work well, but the command line output starts with the following error:
/Users/stephennixon/venv/lib/python3.12/site-packages/fontbakery/fonts_profile.py:103: UserWarning: Failed to load fontbakery.checks.vendorspecific.googlefonts.glyphsets.shape_languages: cannot import name 'Checker' from 'shaperglot' (/Users/stephennixon/venv/lib/python3.12/site-packages/shaperglot/__init__.py)
Expected behaviour
Based on the current adobefonts profile, I wouldn’t expect the
googlefonts.glyphsets.shape_languages
check to run at all, so I wouldn’t expect the warning.Still, I wanted to test the check in general, but even that isn’t working for me:
I also tried:
fontbakery check-googlefonts -c googlefonts.glyphsets.shape_languages <Familyname>/fonts/otf/*.*tf
Both things also failed.
Am I doing something wrong?
Possible related issue/typo?
It does seem like there may be a typo in the legacy check IDs, where the new ID is missing an "s" at the end:
fontbakery/Lib/fontbakery/legacy_checkids.py
Line 70 in ffe83a2
fontbakery/Lib/fontbakery/checks/vendorspecific/googlefonts/glyphsets/shape_languages.py
Lines 9 to 10 in ffe83a2
...but I can’t tell if that is having any impact, here.
It does seem to be correctly referenced in the google fonts profile:
fontbakery/Lib/fontbakery/profiles/googlefonts.py
Line 63 in ffe83a2
Resources and steps needed to reproduce
(Provide the font file that causes the issue, and the exact steps to reproduce it. Also mention the FontBakery version you're using, and some details about your system, e.g. OS, Python version, etc.)
I’ve tried making a clean venv and updating versions of various software, but I’m still running into this.
Versions:
0.13.2
0.6.4
1.1.0
3.12.2
Any insights appreciated here. I’ll try to update if I realize what’s missing.
Thanks!
The text was updated successfully, but these errors were encountered: