Fix unawaited asynch call for python>3.13 (use of nest_asyncio2) - #53
JeanLucPons wants to merge 3 commits into
Conversation
|
@gubaidulinvadim suggested that maybe it can have to do with the jupyter version? This is what I have:
|
|
OK I checked with 3.12 and it was fine. The code i did shoudl only affects >3.13. From Claude: |
|
Here are my version: For py312 env: For py314 |
|
Sorry the patch was incomplete, it can explains what you get. |
|
@TeresiaOlsson the issue you have is unrelated to the one @JeanLucPons solved. But I don't know the origin of it. I was also getting some async-related issues because Python 3.14 changed things. |
Why? I thought the error message Fernando and I see is exactly what @JeanLucPons is trying to solve in this PR? I don't understand why it is related to Python 3.14? For me I have always had it with 3.11 so I don't think it's connected to the Python version. For me it started to appear when the catalog was added. |
|
The error at line 46 in signal .py can appear only from recent version of pyaml_cs_oa (this is linked to a PR from last week) and the bug is well reproductible with python 3.14. The management of the jupyter asynch loop is clearly broken with new python 3.14 asyncio and explains the problem of this PR. I redid few check with the current patch and for me it is fine. |
|
I will try it with different python versions and see if it also fixes it for me. But can't try until Thursday since I'm away on a workshop in AI supported research software engineering for a couple of days. |



This PR fix the following issue in jupyter for python >3.13