-
-
Notifications
You must be signed in to change notification settings - Fork 373
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
_eventloop_set
event called from non-async context
#1292
Comments
mwouts
added a commit
to mwouts/jupytext
that referenced
this issue
Dec 15, 2024
Currently that test fails on the CI, see https://github.com/mwouts/jupytext/actions/runs/12338664239/job/34433965531 A similar report exists already at ipython/ipykernel#1292
mwouts
added a commit
to mwouts/jupytext
that referenced
this issue
Dec 15, 2024
Currently the ipykernel install step fails on the CI, see https://github.com/mwouts/jupytext/actions/runs/12338664239/job/34433965531 A similar report exists already at ipython/ipykernel#1292
mwouts
added a commit
to mwouts/jupytext
that referenced
this issue
Dec 15, 2024
Currently the ipykernel install step fails on the CI, see https://github.com/mwouts/jupytext/actions/runs/12338664239/job/34433965531 A similar report exists already at ipython/ipykernel#1292
mwouts
added a commit
to mwouts/jupytext
that referenced
this issue
Dec 15, 2024
Currently the ipykernel install step fails on the CI, see https://github.com/mwouts/jupytext/actions/runs/12338664239/job/34433965531 A similar report exists already at ipython/ipykernel#1292
mwouts
added a commit
to mwouts/jupytext
that referenced
this issue
Dec 15, 2024
Currently the ipykernel install step fails on the CI, see https://github.com/mwouts/jupytext/actions/runs/12338664239/job/34433965531 A similar report exists already at ipython/ipykernel#1292
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
_eventloop_set
AnyIO event cannot be set here, because it may be called from a non-async context. This event was introduced in #1265 and the issue was revealed in #1291 when running on a trio backend.The text was updated successfully, but these errors were encountered: