[GitHub] [airflow] malthe commented on pull request #20731: Avoid printing a stacktrace for 'AirflowException'-derived errors

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

malthe commented on pull request #20731:
URL: https://github.com/apache/airflow/pull/20731#issuecomment-1007318923


   @ashb I think there are two separate discussions here, one being whether the implementation is complicated and the other which output is the better one.
   
   While the output using the `while tb.tb_next` technique contains the same information, to me it seems a little stuck between two chairs. I think we should either have a full traceback or a simple error message output – the latter is what I have implemented here, the idea being that the user needn't bother with a low-level detail such as a Python traceback in the case where the error is an `AirflowException`.
   
   The error message should be enough to understand what the problem is – and `filename` and `lineno` is really just a bonus then.


-- 
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