Tests fail with pytest-asyncio>=0.25.0

[gepbird]

Tested with textual version 1.0.0 and python version 3.12.8

When updating pytest-asyncio to from 0.24.0 to 0.25.0, some tests start failing:

=========================== short test summary info ============================
FAILED tests/test_focus.py::test_focus_chain - RuntimeError: There is no current event loop in thread 'MainThread'.
FAILED tests/test_focus.py::test_allow_focus - RuntimeError: There is no current event loop in thread 'MainThread'.
FAILED tests/test_focus.py::test_focus_next_and_previous_with_type_selector_without_self - RuntimeError: There is no current event loop in thread 'MainThread'.
ERROR tests/test_focus.py::test_focus_next_wrap_around - RuntimeError: There is no current event loop in thread 'MainThread'.
ERROR tests/test_focus.py::test_focus_next_and_previous - RuntimeError: There is no current event loop in thread 'MainThread'.
ERROR tests/test_focus.py::test_focus_previous_wrap_around - RuntimeError: There is no current event loop in thread 'MainThread'.
ERROR tests/test_focus.py::test_no_focus_empty_selector - RuntimeError: There is no current event loop in thread 'MainThread'.
ERROR tests/test_focus.py::test_wrap_around_selector - RuntimeError: There is no current event loop in thread 'MainThread'.
ERROR tests/test_focus.py::test_focus_next_and_previous_with_type_selector - RuntimeError: There is no current event loop in thread 'MainThread'.
ERROR tests/test_focus.py::test_focus_next_and_previous_with_str_selector - RuntimeError: There is no current event loop in thread 'MainThread'.
ERROR tests/test_focus.py::test_focus_next_and_previous_with_str_selector_without_self - RuntimeError: There is no current event loop in thread 'MainThread'.

Re-running just the failed tests makes them pass, to reproduce this you need to run the whole test suite or at least a larger part.

Possibly related upstream issues:

• 0.25.1 regression Python 3.9 asyncio_mode="auto" # RuntimeError: There is no current event loop in thread 'MainThread' pytest-dev/pytest-asyncio#1039
• Python 3.11: DeprecationWarning: There is no current event loop pytest-dev/pytest-asyncio#757

We noticed this failure in nixpkgs where we recently bumped many python packages and some of textual's tests started failing: https://hydra.nixos.org/job/nixpkgs/trunk/python312Packages.textual.x86_64-linux

Textual Diagnostics

Versions

Name	Value
Textual	1.0.0
Rich	13.9.4

Python

Name	Value
Version	3.12.8
Implementation	CPython
Compiler	GCC 14.2.1 20241116
Executable	/home/gep/.cache/pypoetry/virtualenvs/textual-y4dff5Fy-py3.12/bin/python

Operating System

Name	Value
System	Linux
Release	6.12.10-zen1
Version	#1-NixOS ZEN SMP PREEMPT_DYNAMIC Tue Jan 1 00:00:00 UTC 1980

Terminal

Name	Value
Terminal Application	tmux (3.5a)
TERM	screen
COLORTERM	truecolor
FORCE_COLOR	Not set
NO_COLOR	Not set

Rich Console options

Name	Value
size	width=210, height=54
legacy_windows	False
min_width	1
max_width	210
is_terminal	False
encoding	utf-8
max_height	54
justify	None
overflow	None
no_wrap	False
highlight	None
markup	None
height	None

[TomJGooding]

I'm not familiar with packaging, but FWIW I don't think Textual will currently ever test using the latest version of pytest-asyncio. Textual still supports Python 3.8, whereas it looks like pytest-asyncio now requires Python 3.9.

[gepbird]

Python 3.8 security support ended 4 months ago: https://endoflife.date/python. Is there a specific reason you want to support that?

[Antiz96]

Hi,

Arch Linux package maintainer here, I confirm this issue.
This prevent our textual package from being rebuilt / upgraded.

I'm happy to provide full check logs or test any patches if it helps :)