-
Notifications
You must be signed in to change notification settings - Fork 159
Insights: pytest-dev/pytest-asyncio
Overview
-
- 4 Merged pull requests
- 0 Open pull requests
- 2 Closed issues
- 3 New issues
Could not load contribution data
Please try again later
1 Release published by 1 person
-
v1.0.0 pytest-asyncio 1.0.0
published
May 26, 2025
4 Pull requests merged by 3 people
-
[pre-commit.ci] pre-commit autoupdate
#1131 merged
May 26, 2025 -
Build(deps): Bump coverage from 7.8.0 to 7.8.2 in /dependencies/default
#1130 merged
May 26, 2025 -
Build(deps): Bump hypothesis from 6.131.18 to 6.131.28 in /dependencies/default
#1129 merged
May 26, 2025 -
Remove obsolete test for async fixtures
#1126 merged
May 26, 2025
2 Issues closed by 1 person
-
Not compatible with --doctest-modules --doctest-ignore-import-errors
#797 closed
May 26, 2025
3 Issues opened by 2 people
-
CI: add job that that uses pytest-dev version
#1132 opened
May 27, 2025 -
Incorrect Git ref used when extracting release notes from a tag
#1128 opened
May 26, 2025 -
Missing read permission in ncipollo/release-action
#1127 opened
May 26, 2025
21 Unresolved conversations
Sometimes conversations happen on old items that aren’t yet closed. Here is a list of all the Issues and Pull Requests with unresolved conversations.
-
Harden GitHub Actions workflow
#1122 commented on
May 27, 2025 • 1 new comment -
Improve detection of multiple event loops being requested in a test
#873 commented on
May 26, 2025 • 0 new comments -
test that mark.asyncio scope is respected
#770 commented on
May 26, 2025 • 0 new comments -
Weird interaction with pytest-mock: not requesting event_loop fixture leads to errors
#818 commented on
May 26, 2025 • 0 new comments -
Performance regression in 0.18.1 – 10x slowdown in pytest collection
#997 commented on
May 26, 2025 • 0 new comments -
Decorator type signatures not recognized by pyright
#731 commented on
May 26, 2025 • 0 new comments -
Parameterized asynchronous execution test cases
#694 commented on
May 26, 2025 • 0 new comments -
"The test […] is not an async function" when `asyncio` marker is added via `pytest_collection_modifyitems()`
#810 commented on
May 26, 2025 • 0 new comments -
Synchronize async fixtures dynamically
#668 commented on
May 26, 2025 • 0 new comments -
Type error: `Value of type variable "_R" of function cannot be "AsyncClient"`
#1090 commented on
May 26, 2025 • 0 new comments -
Enable "asyncio debug mode" for default event loop
#980 commented on
May 26, 2025 • 0 new comments -
Allow erroring on remaining tasks after test exit as an option
#1044 commented on
May 26, 2025 • 0 new comments -
Finish deprecation of unset asyncio_default_fixture_loop_scope
#924 commented on
May 26, 2025 • 0 new comments -
Task finalizers run outside of event loop
#878 commented on
May 26, 2025 • 0 new comments -
How to use event_loop_policy without triggering warnings?
#799 commented on
May 26, 2025 • 0 new comments -
Parametrizing `event_loop_policy` parametrizes all tests
#796 commented on
May 26, 2025 • 0 new comments -
Async fixtures may break current event loop
#868 commented on
May 26, 2025 • 0 new comments -
ResourceWarning: unclosed event loop
#724 commented on
May 26, 2025 • 0 new comments -
Dynamically calling async fixture causes a runtime error saying "This event loop is already running"
#112 commented on
May 26, 2025 • 0 new comments -
ContextVar not propagated from fixture to test
#127 commented on
May 26, 2025 • 0 new comments -
loop_scope default
#1095 commented on
May 26, 2025 • 0 new comments