SatyamPandey-07 opened a new issue, #18618:
URL: https://github.com/apache/dolphinscheduler/issues/18618

   ### Search before asking
   
   - [x] I had searched in the 
[issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and 
found no similar feature requirement.
   
   
   ### Description
   
   PR #18615 (addressing #18617) recently fixed the broken Python SDK 
documentation URL in the English `README.md`.
   
   However, several other references across the repository still point to the 
old, broken `https://dolphinscheduler.apache.org/python/main/...` path which 
returns 404:
   
   1. `README_zh_CN.md` (line 16): points to 
`https://dolphinscheduler.apache.org/python/main/index.html` (404)
   2. `docs/docs/en/guide/api/pydolphinscheduler.md` (line 5): points to 
`https://dolphinscheduler.apache.org/python/main/` (404)
   3. `docs/docs/zh/guide/api/pydolphinscheduler.md` (line 5): points to 
`https://dolphinscheduler.apache.org/python/main/` (404)
   4. `AGENT.md` (line 160) & `CLAUDE.md` (line 160): point to 
`https://dolphinscheduler.apache.org/python/main/index.html` (404)
   
   In addition, `docs/docs/en/guide/api/pydolphinscheduler.md` contains minor 
grammar/phrasing inaccuracies ("is python API", "allow you definition", 
"workflow-as-codes") which can be polished to standard terminology 
("workflow-as-code").
   
   All links should be updated to the working documentation index: 
`https://dolphinscheduler.apache.org/python/`.
   
   
   ### Documentation Links
   
   - https://dolphinscheduler.apache.org/python/ (Working - 200 OK)
   - https://dolphinscheduler.apache.org/python/main/ (Broken - 404 Not Found)
   - https://dolphinscheduler.apache.org/python/main/index.html (Broken - 404 
Not Found)
   
   
   ### Are you willing to submit a PR?
   
   - [x] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


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