potiuk closed issue #37484: `_airflow_parsing_context_manager` writes to
os.environ after program has started
URL: https://github.com/apache/airflow/issues/37484
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
potiuk commented on issue #37484:
URL: https://github.com/apache/airflow/issues/37484#issuecomment-1959188687
Yeah. You are completely right that GIL is an extra guard here as well. Even
if you use Threads, in Python, GIL will absolulely prevent two parallel threads
to run C functions like
hterik commented on issue #37484:
URL: https://github.com/apache/airflow/issues/37484#issuecomment-1958850711
Ok, i was not aware how this was used to passed through forks and
subprocesses.
If it's required and you are sure about where this is called it should be
fine. I don't have any
potiuk commented on issue #37484:
URL: https://github.com/apache/airflow/issues/37484#issuecomment-1958442204
Just a comment. I am not sure if that is a problem. If you look at where the
`_airflow_parsing_context_manager` is used, it is used, right before running
subproces.Popen or right
Taragolis commented on issue #37484:
URL: https://github.com/apache/airflow/issues/37484#issuecomment-1948864595
Feel free to raise a PR
--
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
hterik opened a new issue, #37484:
URL: https://github.com/apache/airflow/issues/37484
### Apache Airflow version
2.8.1
### If "Other Airflow 2 version" selected, which one?
_No response_
### What happened?
After observing `_airflow_parsing_context_manager`
