You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hey, hello, as of right now i'm writing this python 3.14 released, and i unexpectedly ran into this problem of pythonnet not supporting python 3.14, so i'm running into this problem too, (runtime error while trying to run a python script that is using pythonnet), i wonder how long it takes to update it for python 3.14 considering its release-candidates and pre-releases have been out for a while
Reacted by GChristensen, mashamellow, IB_U_Z_Z_A_R_Dl and Houbein
Any help is appreciated. There is a branch you can test (#2611), but our CI is currently thoroughly broken and I haven't found the time to fix it, yet.
@filmor I'm unfortunately not in a position to help directly - but if this is a situation that can be fixed by throwing money at someone who does have the skills to investigate the problem, I might be able to help. If that's the case, let me know.
3.1.0rc0 is out now with the Python 3.14 support merged. Please test and report back. I still have not found time to fix the CI completely, which is a prerequisite for me to cut this as a full release.
Reacted by porly1985, Victor, Russell Keith-Magee and PythonPan
@MischaPanch You can take a crack at fixing the two failing tests, if you have time.
The failing unit test blocking 3.14 is test_getting_overloaded_method_binding_does_not_leak_memory, here .
deftest_getting_overloaded_method_binding_does_not_leak_memory():
"""Test that managed object is freed after calling overloaded method. Issue #691"""fromPlainOldNamespaceimportPlainOldClassimportpsutil, os, gc, clrprocess=psutil.Process(os.getpid())
processBytesBeforeCall=process.memory_info().rssprint("\n\nMemory consumption (bytes) at start of test: "+str(processBytesBeforeCall))
iterations=500foriinrange(iterations):
PlainOldClass().OverloadedMethod.Overloads[int]
gc.collect()
System.GC.Collect()
processBytesAfterCall=process.memory_info().rssprint("Memory consumption (bytes) at end of test: "+str(processBytesAfterCall))
processBytesDelta=processBytesAfterCall-processBytesBeforeCallprint("Memory delta: "+str(processBytesDelta))
bytesAllocatedPerIteration=pow(2, 20) # 1MBbytesLeakedPerIteration=processBytesDelta/iterations# Allow 50% threshold - this shows the original issue is fixed, which leaks the full allocated bytes per iterationfailThresholdBytesLeakedPerIteration=bytesAllocatedPerIteration/2>assertbytesLeakedPerIteration<failThresholdBytesLeakedPerIterationEassert903208.96<524288.0tests\test_method.py:1015: AssertionError----------------------------Capturedstdoutcall-----------------------------Memoryconsumption (bytes) atstartoftest: 163160064Memoryconsumption (bytes) atendoftest: 614764544Memorydelta: 451604480===========================shorttestsummaryinfo===========================FAILEDtests/test_method.py::test_getting_overloaded_method_binding_does_not_leak_memory-assert903208.96<524288.0=============1failed, 465passed, 5skipped, 1xpassedin5.02s=============
Additionally, the mono tests fail with an internal error here,
The blocker is #2696 and me travelling. I will get back to this in a week or so. If someone contributes patches for the blocker and the remaining CI issues, that would of course help a lot :)
https://github.com/pythonnet/pythonnet/releases/tag/v3.1.0-rc1 is hopefully the final release candidate. Please test it thoroughly. I will ensure that the changelog is up to date and release it as 3.1.0 next weekend, provided no blockers appear in the meantime.
Reacted by Sebastian Fischer, ghaarsma and pepsibandit
Activity
EliaOndacs commentedon Oct 7, 2025
hey, hello, as of right now i'm writing this python 3.14 released, and i unexpectedly ran into this problem of pythonnet not supporting python 3.14, so i'm running into this problem too, (runtime error while trying to run a python script that is using pythonnet), i wonder how long it takes to update it for python 3.14 considering its release-candidates and pre-releases have been out for a while
filmor commentedon Oct 7, 2025
Any help is appreciated. There is a branch you can test (#2611), but our CI is currently thoroughly broken and I haven't found the time to fix it, yet.
freakboy3742 commentedon Oct 7, 2025
@filmor I'm unfortunately not in a position to help directly - but if this is a situation that can be fixed by throwing money at someone who does have the skills to investigate the problem, I might be able to help. If that's the case, let me know.
NasirNS45 commentedon Oct 29, 2025
Any update on this? Ran into the same issue while installing awsebcli
filmor commentedon Oct 30, 2025
Work is happening in #2611. It works in general, but there are at least two crashes that I (or someone who wants to dive in) have to investigate.
andre-romano commentedon Nov 17, 2025
filmor commentedon Nov 17, 2025
Houbein commentedon Feb 23, 2026
filmor commentedon Feb 25, 2026
3.1.0rc0 is out now with the Python 3.14 support merged. Please test and report back. I still have not found time to fix the CI completely, which is a prerequisite for me to cut this as a full release.
15 remaining items
MischaPanch commentedon Apr 7, 2026
I guess I will have to be patient and somehow circumvent the missing release for now, thanks for the answer
alexchandel commentedon Apr 7, 2026
@MischaPanch You can take a crack at fixing the two failing tests, if you have time.
The failing unit test blocking 3.14 is
test_getting_overloaded_method_binding_does_not_leak_memory, here .Additionally, the mono tests fail with an internal error here,
rayhaze commentedon Apr 7, 2026
filmor commentedon Apr 8, 2026
The blocker is #2696 and me travelling. I will get back to this in a week or so. If someone contributes patches for the blocker and the remaining CI issues, that would of course help a lot :)
alexchandel commentedon Apr 27, 2026
@filmor Do you think that CI failure (
test_getting_overloaded_method_binding_does_not_leak_memory) is a genuine memory leak?dorfman2 commentedon May 6, 2026
filmor commentedon May 16, 2026
https://github.com/pythonnet/pythonnet/releases/tag/v3.1.0-rc1 is hopefully the final release candidate. Please test it thoroughly. I will ensure that the changelog is up to date and release it as 3.1.0 next weekend, provided no blockers appear in the meantime.
ghaarsma commentedon May 20, 2026
Looking forward to the official release. We tested our application with V3.1.0-rc1 and found no issues.
Thanks @filmor , for all your work in getting a Python 3.14 release out the door.
wrichardsonafmil commentedon May 21, 2026
freakboy3742 commentedon May 22, 2026
@filmor I've done another pass of testing with 3.1.0rc1 with Toga's test suite, and didn't spot any problems.