Chore description
Given the number of python packages we host in this repo:
kfp
kfp-server-api
kfp-pipeline-spec
kfp-kubernetes
Each of them use a setup.py for their packaging. As an end user I would like to have a pyproject.toml used for defining the packages' details for their build requirements.
The pyproject.toml has become the recommended way for configuring package related tools/information for targeting different build systems in light of PEP 518 and PEP 621 .
I believe this modern aspect of packaging would ease maintenance by having a central location for dependencies and tool specific settings i.e. pytest, ruff, uv etc.
I would assume there would need to be some sort of hierarchical pyproject.toml structure or either independent ones for each package.
Labels
/area sdk
Love this idea? Give it a 👍.
Chore description
Given the number of python packages we host in this repo:
kfp
kfp-server-api
kfp-pipeline-spec
kfp-kubernetes
Each of them use a setup.py for their packaging. As an end user I would like to have a pyproject.toml used for defining the packages' details for their build requirements.
The pyproject.toml has become the recommended way for configuring package related tools/information for targeting different build systems in light of PEP 518 and PEP 621 .
I believe this modern aspect of packaging would ease maintenance by having a central location for dependencies and tool specific settings i.e. pytest, ruff, uv etc.
I would assume there would need to be some sort of hierarchical pyproject.toml structure or either independent ones for each package.
Labels
/area sdk
Love this idea? Give it a 👍.