-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
total_vec don't exists #1746
Comments
Hi @set92, please upgrade your gensim version |
Im in 3.1.0, and before I was in 3.0.1 but I get the same error. I load a model using |
Yes, you are right, I forgot about wv in |
@menshikh-iv what's the difference between |
@piskvorky we should remove this deprecated methods for avoiding confusion, don't fix. |
Sure, but how can this even happen? How did they get out of sync? I was under the impression the deprecated version is just an alias of the new one (until we remove it for good). |
From the beginning, that's exactly the way it was (i.e. full sync of interfaces), but later - #1256 this PR added |
Yeah, time to remove it. Where do we keep the list of deprecated things + their schedule for removal (version)? Or do you just |
@piskvorky I have no idea, I assume that there is no such list (all these "deprecations" make before I came). The first time, docstrings "forwarding" was added in #1251 (April 11), explicit deprecation added in #1274 (May 3), that looks like a fix for the previous PR. |
My plans are release minor (feature version) on next week and major (with change package structure, removing outdated stuff, etc) in next year (probably in January). |
Let's append a clear deprecation plan with each deprecation: in which version will the code be actually removed? (3.2.0 etc) And then before each release, |
I wanted to save the most important vectors or similar words, but I tried to cut the length of the embeddings using
model.save_word2vec_format('try.c.w2v', total_vec=10000)
but it says total_vec doesn't exists, but it's in the documentation.The text was updated successfully, but these errors were encountered: