Skip to content

While preprocessing the datatable format specification remove any ambiguity#230

Closed
tramora wants to merge 2 commits intodevfrom
208-datatable-format-specification
Closed

While preprocessing the datatable format specification remove any ambiguity#230
tramora wants to merge 2 commits intodevfrom
208-datatable-format-specification

Conversation

@tramora
Copy link
Copy Markdown
Collaborator

@tramora tramora commented Aug 19, 2024

Should (partially) address the issue #208. The remaining fix must be done in khiops-api-base

Copy link
Copy Markdown
Collaborator

@popescu-v popescu-v left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See comments.

@tramora tramora force-pushed the 208-datatable-format-specification branch from 436e870 to f1bc277 Compare August 19, 2024 16:17
@tramora
Copy link
Copy Markdown
Collaborator Author

tramora commented Aug 19, 2024

I just noticed that @folmos-at-orange has already worked on this subject and created the related branch.
The 2 drafts are surely conflicting

@tramora tramora force-pushed the 208-datatable-format-specification branch from f1bc277 to 07c360c Compare August 20, 2024 08:50
task_args["header_line"] = header_line
task_args["field_separator"] = field_separator
detect_format, header_line, field_separator = _preprocess_format_spec(
task_args.get("detect_format", True),
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we need to enforce the True by default here? The default True value of the detect_format kwarg of the API functions is not enough?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It was a preparation of the change in the khiops-api-base (call of the kh._preprocess_tasks_arguments function) where I was not sure a default value of detect_format was set.

By the way I also fixed a problem for tasks that do not have format_spec in their signature.

Thierry RAMORASOAVINA added 2 commits August 22, 2024 10:51
…iguity before sending the parameters to khiops
The `maison` dependency just had a new 2.0 release with breaking changes
(https://github.com/dbatten5/maison/releases/tag/v2.0.0) which break
yamlfix (see lyz-code/yamlfix#286).
@tramora tramora force-pushed the 208-datatable-format-specification branch from 07c360c to 4ae3960 Compare August 22, 2024 08:57
@tramora tramora self-assigned this Sep 24, 2024
@tramora
Copy link
Copy Markdown
Collaborator Author

tramora commented Sep 24, 2024

To be closed as duplicated PR #234

@tramora tramora closed this Sep 24, 2024
@tramora tramora deleted the 208-datatable-format-specification branch October 23, 2024 17:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants