Description
Currently, the Khiops Python library ships with samples of the Core and Sklearn APIs (in the khiops/samples directory), as Python code and Jupyter notebooks.
Moreover, the KhiopsLocalRunner object handles the KHIOPS_SAMPLES_DIR environment variable and maintains several methods dedicated to the management of the samples directory.
However, the Khiops Python library proper is independent of the samples, which are only used in end-to-end testing. The goal of this issue is remove the coupling between the khiops-python proper and the samples, which would be:
- transferred to either
khiops-python-tutorial or khiops-doc(in their notebook and markdown forms) ;
- only used in end-to-end testing in
khiops-python. To this end:
- stop delivering the contents of the
samples/ directory with the khiops package;
- drop
KhiopsLocalRunner support of KHIOPS_SAMPLES_DIR and methods and functions for handling the samples.
Description
Currently, the Khiops Python library ships with samples of the Core and Sklearn APIs (in the
khiops/samplesdirectory), as Python code and Jupyter notebooks.Moreover, the
KhiopsLocalRunnerobject handles theKHIOPS_SAMPLES_DIRenvironment variable and maintains several methods dedicated to the management of the samples directory.However, the Khiops Python library proper is independent of the samples, which are only used in end-to-end testing. The goal of this issue is remove the coupling between the khiops-python proper and the samples, which would be:
khiops-python-tutorialorkhiops-doc(in their notebook and markdown forms) ;khiops-python. To this end:samples/directory with thekhiopspackage;KhiopsLocalRunnersupport ofKHIOPS_SAMPLES_DIRand methods and functions for handling the samples.