[
https://issues.apache.org/jira/browse/AIRFLOW-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Potiuk closed AIRFLOW-1931.
---------------------------------
Resolution: Won't Fix
I am closing some old issues that are not relevant any more. Please let me know
if you want to reopen it.
> Importing airflow module shouldn't affect logging config
> --------------------------------------------------------
>
> Key: AIRFLOW-1931
> URL: https://issues.apache.org/jira/browse/AIRFLOW-1931
> Project: Apache Airflow
> Issue Type: Improvement
> Affects Versions: 1.9.0
> Reporter: Ash Berlin-Taylor
> Priority: Minor
> Fix For: 2.0.0
>
>
> Right now simply importing the airflow main module will alter the logging
> config, which leads to some strange interactions with other python modules.
> (One such example is sphinx autodoc where half the lines are in one logging
> format, and half are in airflow's style after it gets loaded by autodoc.)
> It would be nice if we only used airflow's logging format from within
> airflow.bin.cli.
> More generally this might also be achieved by doing less at the top level of
> modules (for instance importing airflow.configuration will end up creating
> dirs on the filesystem.)
> None of this is a disaster or a bug, it's just a bit tiny bit annoying when
> you use airflow programatically
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
