[GitHub] [airflow] jml commented on issue #5756: [AIRFLOW-5138] Don't override user's warning settings in airflow.configuration

[GitBox <gi...@apache.org>]

jml commented on issue #5756: [AIRFLOW-5138] Don't override user's warning settings in airflow.configuration
URL: https://github.com/apache/airflow/pull/5756#issuecomment-522646250
 
 
   > The problem with not setting this is that by default (since Py3) DeprecationWarning will be silenced, so with this change users would never see Airflow deprecation warnings.
   
   I see.
   
   Since these are warnings are intended for users of the `airflow` executable, rather than people calling Airflow APIs, they should probably be FutureWarnings (as per https://www.python.org/dev/peps/pep-0565/#additional-use-case-for-futurewarning).
   
   Alternatively, the warning should be enabled in the script, not in the configuration module. 

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services