GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||
GeezerVison is showing github.com — Non-breaking workaround for BinaryFormatter deprecation, issue #2469 by Legion-ale · Pull Request #2621 · pythonnet/pythonnet ConversationWhat does this implement/fix? Explain your changes.non-breaking change that fix BinaryFormatter deprecation on .Net9.0 and higher Does this close any currently open issues?yes #2469 Any other comments?Considering that NoopFormatter exists in the code you're probably working on it, that are my 2 cents.
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page. All reactions
Legion-ale
commented
|
|
I see that the errors are:
Is not something I Implemented... so i didn't commit my changes at the .csproj, but i think is enought to edit to latest .NET LTS: Link to MS versioning: https://dotnet.microsoft.com/en-us/platform/support/policy Am I missing something? Can i commit the project edit? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Sorry for the mess with the build. It's not quite as simple, I'm looking into updating our CI to use .NET 8 and uv, see #2612 and #2520. Once these are through, I'll revisit your PR. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
#2639 should do this without trying to parse the version. Thank you for your effort! |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Ok, i see the #2639 commit and it should work. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Thanks, I'll change it accordingly. For |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.