SbloodyS commented on issue #10302: URL: https://github.com/apache/dolphinscheduler/issues/10302#issuecomment-1149420353
> > > FYI, there is a `PythonVirtualenvOperator` in `Apache Airflow` designed in another way. It will automatically created and destroyed virtual env according to the `requirement.txt` provided by users. However, this method seems to require workers to bind public ips. > > > https://github.com/apache/airflow/blob/main/airflow/operators/python.py > > > https://registry.astronomer.io/providers/apache-airflow/modules/pythonvirtualenvoperator > > > > > > Workers that run jupyter tasks maybe always can bing public IPs. In the future maybe we can create a new environment by passing `requirements.txt` and `python version` in > > I plan to add the feature of enabling users to pass requirements.txt to python related task. No matter users choose to bind public ips to their workers or not, what we could do is to provide users with one more choice to manage python environment. `DS` should have the same or even better user experience when it come to python related task environment management. I agreed. It is good to give users a more convenient option. -- 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]
