eladkal commented on code in PR #32832: URL: https://github.com/apache/airflow/pull/32832#discussion_r1284708399
########## docs/apache-airflow/authoring-and-scheduling/plugins.rst: ########## @@ -82,9 +82,9 @@ start of each Airflow process, set ``[core] lazy_load_plugins = False`` in ``air This means that if you make any changes to plugins and you want the webserver or scheduler to use that new code you will need to restart those processes. However, it will not be reflected in new running tasks after the scheduler boots. -By default, task execution will use forking to avoid the slow down of having to create a whole new python -interpreter and re-parse all of the Airflow code and start up routines -- this is a big benefit for shorter -running tasks. This does mean that if you use plugins in your tasks, and want them to update you will either +By default, task execution uses forking. This avoids the slowdown associated with creating a new Python interpreter Review Comment: ```suggestion By default, task execution uses forking. This avoids the slowdown associated with creating a new Python interpreter ``` -- 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]
