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.

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

DOC updated to notebook style for grid_search_text_feature_extraction.py #22558

Merged
merged 7 commits into from
Mar 12, 2022

Conversation

brendo-k
Copy link
Contributor

Reference Issues/PRs

Updated notebook style for examples/model_selection/grid_search_text_feature_extraction.py. Related to #22406

What does this implement/fix? Explain your changes.

Split example into

  • Load categories from the training set
  • Build Pipeline
  • Grid Search

Any other comments?

Can I make edits to the code to make it more clear?

@lesteve lesteve mentioned this pull request Feb 21, 2022
47 tasks
@lesteve lesteve added the Quick Review For PRs that are quick to review label Feb 22, 2022
Comment on lines 49 to 50
# Load categories from the training set
# -------------------------------------
Copy link
Member

Choose a reason for hiding this comment

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

I think this two lines are misplaced, as right below we have all the imports and no training set has been defined. I would keep them in their original position.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

In other accepted pull requests they put the first head above the imports but below the authors, so I put it here to stay consistent with the other pull requests.

Comment on lines 94 to 95
# Grid Search
# -----------
Copy link
Member

Choose a reason for hiding this comment

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

Maybe splitting this as a new cell is not really necessary if my previous comment is taken into account, what do you think?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah I agree. I kept it because it was there previously, but I don't think it is needed

@lesteve
Copy link
Member

lesteve commented Mar 12, 2022

I pushed a few tweaks, pulled upstream/main into your branch (because the doc-min-dependencies was failing). This looks good now, merging, thanks a lot!

@lesteve lesteve merged commit 3a42808 into scikit-learn:main Mar 12, 2022
glemaitre pushed a commit to glemaitre/scikit-learn that referenced this pull request Apr 6, 2022
….py (scikit-learn#22558)

Co-authored-by: Arturo Amor <86408019+ArturoAmorQ@users.noreply.github.com>
Co-authored-by: Loïc Estève <loic.esteve@ymail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentation Quick Review For PRs that are quick to review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants