You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2022/08/18 15:52:25 UTC

[GitHub] [airflow] raphaelauv commented on pull request #25780: Implement ExternalPythonOperator

raphaelauv commented on PR #25780:
URL: https://github.com/apache/airflow/pull/25780#issuecomment-1219659591

   I think `ExternalPythonOperator` is a confusing name , that could give the impression to users that the task is going to run out of airflow itself ( it sounds stupid and magical , but so many airflow users are not aware of how things really works and where code is actually running depending the operator and executor )
   
   Why not add a parameter to PythonVirtualenvOperator giving the possibility to the user to set the path of an existing venv ?
   
   or name this new operator `PythonExistingVirtualenvOperator` ?
   
   thanks
   
   


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