Skip to content
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

Deprecate CLI optimize and delete CLI optimize instruction in examples. #1442

Closed
2 tasks
keisuke-umezawa opened this issue Jun 27, 2020 · 1 comment
Closed
2 tasks

Deprecate CLI optimize and delete CLI optimize instruction in examples. #1442

keisuke-umezawa opened this issue Jun 27, 2020 · 1 comment
Labels
contribution-welcome Issue that welcomes contribution. document Documentation related. feature Change that does not break compatibility, but affects the public interfaces. good first issue Good first issue for contribution.

Comments

@keisuke-umezawa
Copy link
Member

Motivation

The optuna study optimize command has (probably) very few users, but the maintenance cost is high if we try to follow the latest features of the Study.optimize method. Even now, the optuna study optimize command is different from the Study.optimize method because it is not compatible with changes in sampler/pruner. It is better to delete the command itself. So, for the first step, we want to deprecate it and delete corresponding documentation.

Description

  • deprecate optuna study optimize.
  • delete corresponding documentation.
@keisuke-umezawa keisuke-umezawa added document Documentation related. feature Change that does not break compatibility, but affects the public interfaces. contribution-welcome Issue that welcomes contribution. good first issue Good first issue for contribution. labels Jun 27, 2020
@keisuke-umezawa
Copy link
Member Author

Sorry, it has been treated in #1394. I close it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
contribution-welcome Issue that welcomes contribution. document Documentation related. feature Change that does not break compatibility, but affects the public interfaces. good first issue Good first issue for contribution.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@keisuke-umezawa