Skip to content

Create dynamically the khiops execution command from environment variables #356

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
folmos-at-orange opened this issue Feb 10, 2025 · 1 comment
Open

Create dynamically the khiops execution command from environment variables #356

folmos-at-orange opened this issue Feb 10, 2025 · 1 comment
Assignees
@folmos-at-orange
Labels
Priority/2-Low To do after P1 Size/Days Some days of work Status/ReadyForDev The issue is ready to be developed or to be investigated deeply
Milestone
11.0.1.0

Comments

@folmos-at-orange
Copy link
Member

folmos-at-orange commented Feb 10, 2025 •
edited
Loading

Description

Currently, the khiops execution command line is constructed once at startup from the environment variables (usually set by khiops-env). Constructing it dynamically from the environment at each run would:

  • allow to change more easily the settings at each run by avoiding initializing a new runner
  • bring the khiops-python closer to using khiops from a shell
@folmos-at-orange folmos-at-orange added this to the 10.3.0.1 milestone Feb 10, 2025
@folmos-at-orange folmos-at-orange self-assigned this Feb 10, 2025
@folmos-at-orange folmos-at-orange added the Size/Days Some days of work label Feb 10, 2025
@folmos-at-orange folmos-at-orange linked a pull request Feb 19, 2025 that will close this issue
Run initialization integration tests in conda CI #361
Closed
4 tasks
@popescu-v popescu-v removed this from the 10.3.0.1 milestone Feb 20, 2025
@popescu-v popescu-v added Priority/2-Low To do after P1 Status/InDevelopment The issue is in development by one or more team members and removed Priority/0-High To do now labels Feb 20, 2025
@popescu-v
Copy link
Collaborator

popescu-v commented Feb 20, 2025 •
edited
Loading

Depriorized to have the same status as the parent issue: it will wait for the post-v11 release runner refactoring.

@popescu-v popescu-v added this to the 11.0.1.0 milestone Feb 20, 2025
@folmos-at-orange folmos-at-orange removed a link to a pull request Feb 20, 2025
Run initialization integration tests in conda CI #361
Closed
4 tasks
@popescu-v popescu-v mentioned this issue Feb 25, 2025
Closed
4 tasks
@popescu-v popescu-v added Status/ReadyForDev The issue is ready to be developed or to be investigated deeply and removed Status/InDevelopment The issue is in development by one or more team members labels Mar 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@folmos-at-orange folmos-at-orange

Labels
Priority/2-Low To do after P1 Size/Days Some days of work Status/ReadyForDev The issue is ready to be developed or to be investigated deeply
Projects
None yet
Milestone
11.0.1.0
Development

No branches or pull requests
2 participants
@folmos-at-orange @popescu-v