You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2022/01/22 05:17:27 UTC

[GitHub] [airflow] uranusjr commented on pull request #20995: Explicitly set pytest asyncio mode to 'strict'

uranusjr commented on pull request #20995:
URL: https://github.com/apache/airflow/pull/20995#issuecomment-1019060788


   In a very general sense we "should" get more async tests at some point, but we don't "need to" right now IMO; there isn't much to test anyway. `strict` does not really affect the ability to add async tests either, but merely requires async tests (and async fixtures, but we don't have those now and might not need any) to be explicitly marked, while `auto` makes those explicit markers optional. So setting `strict` now is the safest option and will not have any consequences if we ever decide to switch to `auto`.


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org