Skip to content
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

chore: use AnyIO 4.0+ in tests dependencies #663

Merged
merged 1 commit into from
Oct 20, 2023
Merged

Conversation

dlax
Copy link
Contributor

@dlax dlax commented Oct 18, 2023

Fix #662

@dlax dlax force-pushed the anyio4 branch 2 times, most recently from 07a5f64 to 232ca8f Compare October 18, 2023 09:41
We set the 'loop_factory' asyncio option for parametrizing the
anyio_backend() fixture as anyio 4.0 has replaced the 'policy' option by
'loop_factory'.

In tests/pool/test_pool_async_noasyncio.py, we previously used
the anyio_backend_options fixture to retrieve the loop policy; now we
build it directly. This could be improved by using the loop_factory, but
only from Python 3.11 with an asyncio.Runner().
@dlax dlax marked this pull request as ready for review October 18, 2023 11:03
@dvarrazzo dvarrazzo merged commit 20b64db into psycopg:master Oct 20, 2023
38 checks passed
@dvarrazzo
Copy link
Member

Thank you very much for the chore, @dlax!

@dlax dlax deleted the anyio4 branch October 20, 2023 18:56
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.

Resolve problems with anyio 4
2 participants