Skip to content

put in version_added label#15973

Closed
reshamas wants to merge 51 commits intoscikit-learn:masterfrom
reshamas:adding_version
Closed

put in version_added label#15973
reshamas wants to merge 51 commits intoscikit-learn:masterfrom
reshamas:adding_version

Conversation

@reshamas
Copy link
Copy Markdown
Member

Reference Issues/PRs

Fixes part of Issue #15426
Closes #15482

What does this implement/fix? Explain your changes.

Towards the upcoming release of v0.22, it would be useful if some contributors (or sprinters) scoured the change log and identified whether any added/changed parameters/classes needed a versionadded or versionchanged label, and to produce pull requests adding them when otherwise omitted.

Any other comments?

Continuing work begun by @alekslovesdata at SF scikit sprint (Nov 2019)

Circe McDonald and others added 30 commits November 2, 2019 11:37
@reshamas
Copy link
Copy Markdown
Member Author

@rth @jnothman
This PR is ready for review.

I could not figure out why the _target.py file was throwing the linting error, so removed it. I can add it back in if you have any advice on the formatting to update.

@cmarmo this is the last PR from the SF sprint.

@cmarmo
Copy link
Copy Markdown
Contributor

cmarmo commented Dec 26, 2019

@reshamas , the double * is interpreted by sphinx as a bold formatting start without end-formatting.
To avoid the warning you could write ``**param``. This will be rendered as **param: I'm not sure this is standard for skl documentation, but the warning will be gone.

@reshamas
Copy link
Copy Markdown
Member Author

thanks @cmarmo. that worked! 👏

@cmarmo
Copy link
Copy Markdown
Contributor

cmarmo commented Dec 29, 2019

@jnothman , @amueller , @TomDLT , you reviewed the original PR.
Could you please check this one, as we can close the SF sprint list? Thanks for your collaboration!

Copy link
Copy Markdown
Member

@jnothman jnothman left a comment

Choose a reason for hiding this comment

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

Thanks for the work.

Several version labels are incorrect, so I cannot trust the method used to produce them.

-------
self : object

.. versionchanged:: 0.22
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Numpydoc won't process this correctly, since it's in the Returns section

I'm not sure whether we need such notes, but they have to appear in a Notes section or in the top description section.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I don't think such a bug fix requires that note anyway.

out of the raw, unprocessed input.

.. versionchanged:: 0.21
.. versionadded:: 0.21
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

analyzer was added long before version 0.21. It should not be marked as added in 0.21.

I'm not sure what this versionchanged intends to refer to, and unless its referent can be clarified, the versioning note should be removed.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Ah... I think the versionchanged is with reference to the following content, which should be indented.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

This was marked as resolved but @jnothman's comment still holds: the analyzer param was not added in 0.21, it is much older. It was changed in 0.21 as explained in the next paragraph. The previous annotation was correct.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I marked things as resolved as I fixed them, but I coudn't push to the repo. Created a new PR: #16015

If a callable is passed it is used to extract the sequence of features
out of the raw, unprocessed input.

.. versionchanged:: 0.21
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

the versionchanged is with reference to the following content, which should be indented.

Introduction to Information Retrieval. Cambridge University
Press, pp. 118-120.

.. versionadded:: 0.19
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Firstly, this should not be in the References section.

Secondly, TfidfTransformer was not added as late as version 0.19. It was added in version 0.5 as far as I can tell!

How did you decide it was added in 0.19, and is it possible you could check for similar errors.

@glemaitre
Copy link
Copy Markdown
Member

I'll make a second review once @jnothman are addressed.

@reshamas
Copy link
Copy Markdown
Member Author

reshamas commented Jan 3, 2020

I propose closing this PR which I took over from SF sprint.

  • I think it is best practice to not include that many files in one PR
  • For the upcoming Berlin beginner sprint, suggestion for new contributors is:
  1. include only 2 files in each PR
  2. link to the change log in the comments section so it can be verified.

cc: @adrinjalali @cmarmo

@adrinjalali
Copy link
Copy Markdown
Member

I agree.

@glemaitre
Copy link
Copy Markdown
Member

I propose closing this PR

It is costly on the reviewing side since @jnothman already make an entire review.

I agree that the PR is not ideal but I would prefer to quickly fix the comments and merge.

For the next PR, we could ask to cut the PR into smaller PRs before starting the review process.

@cmarmo
Copy link
Copy Markdown
Contributor

cmarmo commented Jan 3, 2020

I propose closing this PR

It is costly on the reviewing side since @jnothman already make an entire review.

@glemaitre, you are right, but the problem here is that @reshamas is not the original author of the PR and some of the comments are related to choices made by the first author.
I think that @jnothman deserves our excuses, and we all have probably to learn how more efficiently manage PR from beginner sprints.
I will reorganize the corresponding issue #15426 for the next two sprints... and ensure that @jnothman recommendations will be taken into account. Is that solution satisfying?

@adrinjalali
Copy link
Copy Markdown
Member

I'll take over and apply the requested changes for us to close this PR, that's probably easier.

@cmarmo
Copy link
Copy Markdown
Contributor

cmarmo commented Jan 3, 2020

I'll take over and apply the requested changes for us to close this PR, that's probably easier.

As you wish, but this is indeed a nice beginner's issue because it forces to look in the scikit-learn API.
Let's see if @jnothman will forgive us, first? :)

@adrinjalali
Copy link
Copy Markdown
Member

hmm, seems like maintainers can't update this PR?

@reshamas
Copy link
Copy Markdown
Member Author

reshamas commented Jan 3, 2020

This PR is marked with "allow edits from maintainers".
not sure about the previous PR.

@glemaitre
Copy link
Copy Markdown
Member

Closing this PR. We put back the estimator in the pool of the main issue for the next sprint.

@glemaitre glemaitre closed this Jan 9, 2020
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.

8 participants