Hi Jay, I'm definitely +1 to this. Putting py code in another repo will reduce the CI running time of both sides. Just curious, as we discussed before in a community conference, another purpose for separating py code is that we expect a faster iteration of pyds. If we `release Python API as the same version of dolphinscheduler`, how could we achieve that?
Thanks. *Best Regards,* *Chufeng (Eric) Gao* On Wed, Nov 2, 2022 at 5:30 PM Jiajie Zhong <[email protected]> wrote: > I propose to separate Python API code into another repository to > maintenance, and release Python API in an independent process with an > independent version > > Currently our Python API code is a module in apache/dolphinscheduler > codebase, each time users change Python API code, they need to run all > requests CI check for dolphinscheduler and Python API, But if the user > does only change Python code, it could be merged if Python API CI pass > and do not dependent on others CI. > > Besides, we release Python API as the same version of > dolphinscheduler. It is easy for user to match Python API version. But > when Python API does not change any code, but dolphinscheduler release > a bugfix version, Python API has to release the new version to match > dolphinscheduler. This happened when we released Python API 2.0.6 and > 2.0.7. 2.0.6 and 2.0.7 is bugfix version, and Python API does not > change any code, so the PyPI package is the same. > > Separate Python API also makes our code more sense, we will have more > distinguished code in dolphinscheduler and Python API new repository. > Have separate > issue tracker and changelog for information to users. > > -- > Best Wish > — Jay Chung >
