Skip to content

Conversation

balos1
Copy link
Member

@balos1 balos1 commented Sep 20, 2025

This is the changes that are needed to enable the Python interfaces without the bindings themselves included to make the review process easier.

@balos1 balos1 changed the base branch from develop to feature/python-interfaces September 22, 2025 17:33
@balos1
Copy link
Member Author

balos1 commented Sep 22, 2025

@gardner48 When this is merged into the feature/python-interfaces branch, I don't want the commits squashed so that I don't get a bunch of merge conflicts between this part1 branch and part2.

@balos1 balos1 removed the dont-merge label Sep 22, 2025
@gardner48
Copy link
Member

General question on the C++ wrappers, how is error handling done? For examples, what happens if one of the C constructors returns NULL?

@balos1
Copy link
Member Author

balos1 commented Oct 3, 2025

General question on the C++ wrappers, how is error handling done? For examples, what happens if one of the C constructors returns NULL?

The view will just hold a NULL object and error handling will be deferred to when it is used.

@balos1 balos1 requested a review from gardner48 October 6, 2025 20:29
@balos1 balos1 merged commit 0ea9715 into feature/python-interfaces Oct 7, 2025
52 of 54 checks passed
@balos1 balos1 deleted the feature/python-part1 branch October 7, 2025 17:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants