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

tests: catch ClipperException when calling Execute before any AddPath #14

Merged
merged 1 commit into from
Jan 9, 2018

Conversation

anthrotype
Copy link
Member

Calling Execute on an empty Pyclipper instance would silently pass without exception in previous pyclipper 1.0.7 with Clipper lib version 6.2.1.
Now, the Clipper::Execute method returns unsuccessful if called before any AddPath
or AddPaths, so pyclipper duly raises an exception.

Client code may need to be adjusted accordingly.

Calling `Execute` on an empty `Pyclipper` instance would silently pass
without exception in previous pyclipper 1.0.7 with Clipper lib version 6.2.1.
Now, the `Clipper::Execute` method returns unsuccessful if called before any
`AddPath` or `AddPaths`, so pyclipper duly raises an exception.
anthrotype added a commit to googlefonts/fontmake that referenced this pull request Jan 8, 2018
or else with pyclipper 1.1.0 we get a pyclipper.ClipperException:
See fonttools/pyclipper#14
@anthrotype anthrotype merged commit e772bd9 into fonttools:master Jan 9, 2018
@anthrotype anthrotype deleted the test-empty-clipper branch January 9, 2018 11:34
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.

1 participant