mathbou commented on PR #30367: URL: https://github.com/apache/airflow/pull/30367#issuecomment-1490325584
To give more context, with the `debug` level logging, here is the output of https://github.com/apache/airflow/blob/6e751812d2e48b743ae1bc375e3bebb8414b4a0e/airflow/operators/python.py#L695-L697 ``` [2023-03-30T12:40:46.882+0000] {settings.py:267} DEBUG - Setting up DB connection pool (PID 170) [2023-03-30T12:40:46.882+0000] {settings.py:372} DEBUG - settings.prepare_engine_args(): Using pool settings. pool_size=5, max_overflow=10, pool_recycle=1800, pid=170 2.5.2 [2023-03-30T12:40:46.908+0000] {settings.py:408} DEBUG - Disposing DB connection pool (PID 170) ``` The same call with a `>=info` logging level only returns the version number `2.5.2`. --- About side effects, from what I test and read in the source code, there shouldn't be any. I saw the warning when digging to understand what Airflow was doing on import, especially to understand why it was initializing itself on its own. From my understanding, there's no point, for a version query and specifically this call, that Airflow initialize itself, this command should only get the value from the module, no more, no less. --- I'm not sure to fully understand your point here: > Changing production behaviour in order to make "DEBUG" settings behave wrongly -- 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-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
