jiengup commented on PR #4421: URL: https://github.com/apache/iggy/pull/4421#issuecomment-6059555501
@slbotbm I checked the Python SDK and BDD tests and found no use of an asyncio API that would prevent them from moving from Python 3.10 to 3.11. BDD steps call asyncio.run() (https://docs.python.org/3.11/library/asyncio-runner.html#asyncio.run), available since 3.7; SDK tests also use asyncio.to_thread() (https://docs.python.org/3.11/library/asyncio-task.html#asyncio.to_thread), available since 3.9. The relevant 3.11-only API is asyncio.Runner (https://docs.python.org/3.11/library/asyncio-runner.html#asyncio.Runner), which pytest-asyncio uses internally. Its v1.4.0 source (https://github.com/pytest-dev/pytest-asyncio/blob/6e14cd2af9292dca1fa2b027a06bbc40b0e0e425/pytest_asyncio/plugin.py#L57) imports the standard-library Runner on Python 3.11+ and a backport on older versions(. That explains why backports-asyncio-runner disappeared from the regenerated lock files. On Python 3.11.16, the local SDK unit run passed 220 tests. Server-backed integration and BDD tests were not run as part of this check, so their runtime behavior still needs CI verification. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
