Repository navigation
Fixes for shift from python 2 C-API to python 3 C-API for new SWIG 4.5.0 Version - #585
Merged
Merged
Conversation
rafaelab
self-requested a review
August 28, 2026 13:15
rafaelab
approved these changes
Aug 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi,
in this PR I want to introduce the fixes so we are able to use the new SWIG 4.5.0 Version (Detailed Release Notes).
I further more add the new flag
-pyito generate stub files with swig in case the swig version is at least 4.5.0, this replaces pybind in this case.Lastly, I change the autodoc number to a more detailed version and add the
-nogiland-threadsflag to tell python>=3.13 that we do not need thread protection and in turn are able to utilize (hopefully) more resources.This fixes #584 !