-
-
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
Gensim's FastText model reads in unsupported modes from Facebook's FastText #3179
Comments
may I work on this? |
Sure. |
Since there is no commits for a month, can I take up this task? |
#3222 I have tried to add error handling before loading another fasttext model to gensim/fasttext. |
Hi, is this issue still available to be worked on? Would love to get started with contributions on this project! |
would love to start contributing to this repo by starting with this issue, can it be assigned to me? |
You don't need to be assigned something to propose a fix, in the form of a Github PR. This is a very low-stakes matter - less-used (fairly obscure) FastText modes, with few people expecting them to work in Gensim. It's unclear that the gap here has ever actually inconvenienced or confused anyone – it's just a matter of being clear/thorough in describing what actually works, "just in case". So improvements should stay safe/minimal/easy-to-review/low-risk - for example, it might just be some extra clarity in related doc-comments (to note not all modes fully supported). Maybe, also, some warning sent in user-visible output (with same conventions as similar warnings elsewhere in Gensim) if/when unsuppored modes are loaded - if it can be done simply. |
Okay, will look forward for more impactful problems to solve then |
This would still be a fine first issue, for which improvements wquld be welcome! My comment was meant to help describe the kind of (careful, minimal, straightforward) contribution that would make sense for this sort of "loose ends" issue. |
Sure makes sense |
In gensim/models/fasttext.py:
The text was updated successfully, but these errors were encountered: