Silence deprecations in Python 3.14#1111
Conversation
seifertm
force-pushed
the
support-python3.14
branch
3 times, most recently
from
d7ba2cc to
0b67394
Compare
|
The changes were successfully tested locally using Python 3.14-alpha7. Either we block this PR until tox-dev/tox#3523 is addressed or we pin the version of Python 3.14 to "3.14-alpha7" in the CI. |
|
Could also mark non-final versions as allowed to fail. |
The tests are interdependent and are more concerned with testing pytest's fixture finalizer functionality than pytest-asyncio.
seifertm
force-pushed
the
support-python3.14
branch
from
0b67394 to
a2fa4c6
Compare
Python 3.14 is still in development, so errors when testing against pre-releases are expected.
seifertm
force-pushed
the
support-python3.14
branch
from
a2fa4c6 to
6f197a5
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1111 +/- ##
==========================================
+ Coverage 89.63% 89.93% +0.30%
==========================================
Files 2 2
Lines 434 447 +13
Branches 53 53
==========================================
+ Hits 389 402 +13
Misses 30 30
Partials 15 15 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
I'm not sure if this makes a difference for pytest-asyncio, but FYI |
This has now been fixed in tox: https://github.com/tox-dev/tox/releases/tag/4.26.0 |
|
@bdarnell I wasn't aware that the deprecation of I don't think it's relevant for pytest-asyncio, because the current plan is to transition everything to asyncio.Runner. |
5 participants
Silences deprecations of:
asyncio.get_event_loop_policy()asyncio.set_event_loop_policy()asyncio.set_event_loop()Although this is not a permanent fix, it prevents people from having to deal with deprecation warnings caused by pytest-asyncio when testing against Python 3.14.
A long-term solution to the deprecations involve:
event_loop_policyfixtureasyncio.Runnerto run the testsCloses #1025