Port fix for .NET 9 from IronLanguages/ironpython3#1807 to ironpython2 #842
+1
−0
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
|
Would love to get this fix in and a release out, we just ran into this trying to upgrade to .NET 9. |
|
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.
Latest IronPython2 does not work on .NET 9.
Submission containing materials of a third party: This fix comes from IronLanguages/ironpython3#1807 specifically: IronLanguages/ironpython3@9c2e61c
Worth noting that IronPython2 does not build using the script in its current state, but can be built after updating DLR to v1.3.2 and applying attached patches to IronPython2 and DLR.
patches.zip
Patches mostly disable analyzers and audits, so probably shouldn't be merged to master but might be useful to anyone trying to build it from source.