Skip to content
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

Use MathGlyph's "strict" flag #962

Merged
merged 5 commits into from
Dec 8, 2022
Merged

Conversation

justvanrossum
Copy link
Contributor

This fixes #961, and makes instantiator.py as strict as varLib when interpolating.

Depends on robotools/fontMath#305, though, as fontMath doesn't properly propagate its "strict" flag down to copies.

So this PR should probably also update its fontMath version dependency, once a new fontMath is out.

This fixes googlefonts#961, and makes instantiator.py as strict as varLib when interpolating.

Depends on robotools/fontMath#305, though, as fontMath doesn't properly propagate its "strict" flag down to copies.

So this PR should probably also update its fontMath version dependency, once a new fontMath is out.
Copy link
Member

@anthrotype anthrotype left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, pending the other upstream change

@anthrotype
Copy link
Member

ideally we also add a test perhaps based on the one from #961

@justvanrossum
Copy link
Contributor Author

That failing lint check seems to demand passing the strict kw arg to builtin zip. This was introduced in 3.10, so as long as we need to support Python < 3.10, this lint check seems overly aggressive.

Not sure what to do about that in the context of this PR.

@anthrotype
Copy link
Member

for now, we need to mute that overly zealous flake8 warning with googlefonts/ufo2ft#684

@anthrotype
Copy link
Member

i'm fine if you do that within this same PR, thanks!

@anthrotype
Copy link
Member

anthrotype commented Dec 8, 2022

oh jeez, codecov is haunting us again here.. ignore it for now, I can fix it on main

@anthrotype
Copy link
Member

@justvanrossum do you mind if I merge as is? I can fix the unrelated CI failures on main afterwards

@justvanrossum
Copy link
Contributor Author

Oh I just added a test! Sure, I'm fine with merging if you consider it fine.

@anthrotype
Copy link
Member

can you please rebase on main? I think I fixed both flake8 and codecov issues

Copy link
Member

@anthrotype anthrotype left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

test also LGTM

@anthrotype
Copy link
Member

just pushed v3.5.1 tag 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

fontmake -i destroys geometry when off curve points coincide with on curve points
2 participants