EricGao888 commented on a change in pull request #713:
URL: 
https://github.com/apache/dolphinscheduler-website/pull/713#discussion_r840254198



##########
File path: docs/en-us/dev/user_doc/guide/task/python.md
##########
@@ -1,15 +1,55 @@
 # Python Node
 
-- Using python nodes, you can directly execute python scripts. For python 
nodes, workers use `python **` to submit tasks.
+## Overview
 
-> Drag from the toolbar 
![PNG](https://analysys.github.io/easyscheduler_docs_cn/images/toolbar_PYTHON.png)
 task node to the canvas, as shown in the following figure:
+`Python Task` is used to create a python-type task and execute python scripts. 
When the worker execute `Python Task`,
+a temporary python script is generated, and the Linux user with the same name 
as the tenant executes the script.
 
-<p align="center">
-   <img src="/img/python-en.png" width="80%" />
- </p>
+## Create Task
 
-- Script: Python program developed by the user.
-- Environment Name: Specific Python interpreter path for running the script. 
If you need to use Python **virtualenv**, you should create multiply 
environments for each **virtualenv**.  
-- Resources: Refers to the list of resource files that need to be called in 
the script.
-- User-defined parameter: It is a user-defined local parameter of Python, and 
will replace the content with `${variable}` in the script.
-- Note: If you import the python file under the resource directory tree, you 
need to add the `__init__.py` file.

Review comment:
       @zhongjiajie @Tianqi-Dotes Is there anything else I could do here? I 
mean the docs overwrite stuff, not sure what it is.




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


Reply via email to