potiuk opened a new issue, #33692: URL: https://github.com/apache/airflow/issues/33692
### Discussed in https://github.com/apache/airflow/discussions/33052 <div type='discussions-op-text'> <sup>Originally posted by **notatallshaw-gts** August 2, 2023</sup> 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.</div> -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
