Exceptions become a mess in logs using a Python 3.11 docker operator #33692
Description
Discussed in #33052
Originally posted by notatallshaw-gts August 2, 2023
We drive a lot of our scripts via the DockerOperator as we define our Python script environment separately from our Airflow environment.
Recently we upgraded our script environment to Python 3.11 and an issue has come up using the default Airflow log capturing, Python 3.11 introduced these nice arrows: https://realpython.com/python311-error-messages/#improvements-in-python-311
But they don't always stay on one line in the Airflow logs and can end up looking a bit of a mess, e.g. here is a snippet of part of an exception in one of our logs:
File "/usr/local/lib/python3.11/site-packages/click/core.py", line 1130, in __call__
return self.main(*args, **kwargs)
^^^^
^^^^^^
^^^^^^^
^^^^^^^
^^
File "/usr/local/lib/python3.11/site-packages/click/core.py", line 1055, in main
rv = self.invoke(ctx)
^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/click/core.py", line 1404, in invoke
return ctx.invoke(self.callback, **ctx.params)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/click/core.py", line 760, in invoke
return __callback(*args, **kwargs)
^^^^^^^^^^^^
^^^^^^^^^
^^^^^^
Has anyone else suffered this and fixed it? Or would someone be able to give some hints on maybe how to solve this.