Open merelcht opened 1 year ago
Steps to complete:
Investigate each of the suggested tools (tox, nox, and hatch). Analyze their features, capabilities, and limitations. Consider the specific requirements of kedro-plugins
.
Look for reviews, comments, and feedback from the community who have experience using these tools. Their experiences and insights can help.
Evaluate the quality of documentation and support available for each tool. This is important for the long-term maintainability of the chosen solution.
If possible, conduct a test of each tool. To help gauge the ease of setup, execution, and troubleshooting for each tool.
Present the findings and comparisons
Since this issue was opened, the CI has changed and I don't think we're using conda to install complex dependencies anymore? Maybe tox4 could be reconsidered.
I have no experience with nox nor hatch. About the latter, not sure how compatible it would be with our setuptools-based projects.
Description
Decide on a tool to use to make it easier to test the plugins in
kedro-plugins
individually.Context
The plugins are all in a mono-repo, but are not related and so they all require slightly different run environments.
Possible Tools
Issue outcome
Decision on which tool to use. This ticket should be a spike. The implementation of the tool is a separate task.