RELEASE v0.2.1 #38
Merged
RELEASE v0.2.1 #38
Conversation
This file contains 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
Only a stub with pointer to the main function left in me. This means mex file has no link to Python (all calls to Python handled inside libpymcr) so we can handle the ABI changes >3.11
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.
The real
0.2release - fixes some bugs found when testing 0.2 pre-release with pace-python:ctfarchivecall_pythoncall_pythonmex file to not link at all with Python - to overcome ABI changes between 3.11, 3.12 and 3.13. This allows us to ship a singlemexfile in thectfrather than having one for each Python release. The maincall_pythoncode is now included inlibpymcrrather than themex-file.