python module compatability with SWIG 4.3.0+ for AppendOutput. #573
Conversation
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
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.
See the following:
https://sourceforge.net/projects/swig/files/swig/swig-4.3.0/#:~:text=New%20declaration%20of%20SWIG_Python_AppendOutput%20is,now
Alternatively, there's a macro approach that was set up:
swig/swig#2907
Thus far I found with the core & vehicle python modules, only the chmatrix.i in core raises the issue. Also I found the older appendoutput with 2 args is also in Chrono's numpy.i under sensors (though i haven't compiled or tested that module) - presumably the same fix/upgrade could be applied there, or alternatively make use of the SWIG macro for a global approach :)