Skip to content

Conversation

@cjdoris
Copy link
Member

@cjdoris cjdoris commented Nov 14, 2025

see the updated faq for why

@cjdoris cjdoris merged commit 6b385d6 into main Nov 14, 2025
16 checks passed
@cjdoris cjdoris deleted the no-python-3.14 branch November 14, 2025 22:06
@PallHaraldsson
Copy link
Contributor

PallHaraldsson commented Nov 20, 2025

Your version restriction in PythonCall.jl applies to juliacall automatically I believe.

Are you sure the problem also applied to calling from Python? I asked the Google search AI, and it it seemed to agree (though I wasn't sure either way). I think the support restriction should also go into the README.md; because it only applies to last version, right? It's a bit hard (impossible?) to do retroactively, and the older versions will error. What the AI told me (presumably Gemini, maybe latest 3 (which claims and seems great), though likely still using older Gemini 2.5 flash?):

JuliaCall (the Python library counterpart) is also broken by this change for the same fundamental reasons. It's an issue with the underlying mechanism of calling back and forth between the two runtimes when using stack switching. The issue is a core one that the Python core developers are discussing, and a fix is not trivial as it involves assumptions about the C ABI and stack pointers.

@cjdoris
Copy link
Member Author

cjdoris commented Nov 22, 2025

Yes the issue holds from Julia or from Python, it just surfaces a lot faster from Julia - I think it's the REPL using multiple tasks, one for the REPL itself and one to evaluate code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants