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.
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
Expose params
/ ParamsDependency
in the Python API.
#6507
Comments
params
/ ParamDependency
in the Python API.params
/ ParamsDependency
in the Python API.
For reference, open source project implementing an API similar to what it's described in the issue https://docs.orchest.io/en/stable/fundamentals/sdk/index.html#api-parameters |
How would DVC know what stage this Python file is associated with? Would it only work automatically if the file is in the UPDATE: Answer in #7613 |
Closes #6507 Uses `repo.params.show` with custom error_handler and postprocess the outputs for more user-friendly structure. Extend `repo.params.show` to accept `stages` argument to cover the "params of current stage" use case.
Closes #6507 Uses `repo.params.show` with custom error_handler and postprocess the outputs for more user-friendly structure. Extend `repo.params.show` to accept `stages` argument to cover the "params of current stage" use case.
Closes #6507 Uses `repo.params.show` with custom error_handler and postprocess the outputs for more user-friendly structure. Extend `repo.params.show` to accept `stages` argument to cover the "params of current stage" use case.
Closes #6507 Uses `repo.params.show` with custom error_handler and postprocess the outputs for more user-friendly structure. Extend `repo.params.show` to accept `stages` argument to cover the "params of current stage" use case.
Closes #6507 Uses `repo.params.show` with custom error_handler and postprocess the outputs for more user-friendly structure. Extend `repo.params.show` to accept `stages` argument to cover the "params of current stage" use case.
Closes #6507 Uses `repo.params.show` with custom error_handler and postprocess the outputs for more user-friendly structure. Extend `repo.params.show` to accept `stages` argument to cover the "params of current stage" use case.
Closes #6507 Uses `repo.params.show` with custom error_handler and postprocess the outputs for more user-friendly structure. Extend `repo.params.show` to accept `stages` argument to cover the "params of current stage" use case.
Closes #6507 Uses `repo.params.show` with custom error_handler and postprocess the outputs for more user-friendly structure. Extend `repo.params.show` to accept `stages` argument to cover the "params of current stage" use case.
params
are easy to include in a pipeline via templating but using them inside a python script might not be that trivial and require several changes in the user's code (i.e. when a stage uses several params from different params files).I think that it would be nice to expose some function in the public API that would take care of loading the
params
associated to a stage and returning them as python objects, directly usable in the python script.It could be something like
dvc.api.get_params()
and would take care of loading only the params defined in theparams
section of the stage.The text was updated successfully, but these errors were encountered: