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

Docs for word2vec.py forwarding functions and one more #1251

Merged
merged 2 commits into from
Apr 10, 2017

Conversation

shubhvachher
Copy link
Contributor

Do you think we should add depreciated warnings to these forwarding functions as well? @gojomo.

Quoting @tmylk for Word2Vec class.

Please avoid adding new forwarding functions. KeyedVectors is the way to go.

@shubhvachher
Copy link
Contributor Author

A lot of new people consider the documentation for gensim to be incomplete or done poorly. This should help fix that for the Word2Vec class.

@tmylk tmylk merged commit 83c33c8 into piskvorky:develop Apr 10, 2017
Please refer to the documentation for
`gensim.models.KeyedVectors.most_similar`
This is just a forwarding function.
In the future please use the `gensim.models.KeyedVectors` instance in wv
Copy link
Owner

Choose a reason for hiding this comment

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

Strange line breaks + docstring a bit obscure. I'm not sure reading this would help me if I didn't already know what it's talking about.

How about simply Deprecated; use self.ww.most_similar() instead.?

Same with all the other "forwarding" functions.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Hmm, The strange line breaks were added by me in the fix pep8 commit! I'm new to following pep8 all the time, do you think I overdid it there?

Is a depreciated warning to be added to these methods? Will they become unavailable in a later version? If yes, then this should surely be changed asap and I'll send a new PR with the same.

Copy link
Owner

@piskvorky piskvorky Apr 11, 2017

Choose a reason for hiding this comment

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

It's a question for @tmylk , but I think we want to nudge users toward using the new API, yes.

The line breaks are definitely not good, hurts readability.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ok, changes made as suggested. #1274

Thanks for the line breaks tip 👍 . Will line break only if comments go excessively above PEP8 standards!

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.

3 participants