You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I searched the issues and found no similar issues.
Component
Transforms/Other
Feature
The current flat structure for the transform and the lack of package name for each transform makes it counter-intuitive to package all the transforms in a single wheel using standard python tools. Since none of the transform currently use a package name, all the source code need to be copied into the same folder in post-release step in order to publish all the transforms in a single wheel to pypi.
If each transform has its own namespace, than the packaging and distribution will be greatly simplified by specifying the package name and package code folder in the pyproject.tml as follow:
tool.setuptools.package-dir]
dpk_code_quality = "../../code/code_quality/python/src"
dpk_code_quality = "../../code/code_quality/ray/src"
....
]
Are you willing to submit a PR?
Yes I am willing to submit a PR!
The text was updated successfully, but these errors were encountered:
Search before asking
Component
Transforms/Other
Feature
The current flat structure for the transform and the lack of package name for each transform makes it counter-intuitive to package all the transforms in a single wheel using standard python tools. Since none of the transform currently use a package name, all the source code need to be copied into the same folder in post-release step in order to publish all the transforms in a single wheel to pypi.
If each transform has its own namespace, than the packaging and distribution will be greatly simplified by specifying the package name and package code folder in the pyproject.tml as follow:
tool.setuptools.package-dir]
dpk_code_quality = "../../code/code_quality/python/src"
dpk_code_quality = "../../code/code_quality/ray/src"
....
]
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: