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

Warnings with spacy version 2.3.4 #2

Open
nicolamassarenti opened this issue Dec 11, 2020 · 1 comment
Open

Warnings with spacy version 2.3.4 #2

nicolamassarenti opened this issue Dec 11, 2020 · 1 comment

Comments

@nicolamassarenti
Copy link

nicolamassarenti commented Dec 11, 2020

Hi Martino,

I've seen your implementation and it is really usefull. Great work!

My environment runs with python 3.7.9 and spacy 2.3.4.
I've installed the package as you suggested in the readme, so with this command

pip install -U https://github.com/MartinoMensio/it_vectors_wiki_spacy/releases/download/v1.0.1/it_vectors_wiki_lg-1.0.1.tar.gz

I am able of running spacy with your embeddings but I have the following warnings.

.../python3.7/site-packages/spacy/util.py:275: UserWarning: [W031] Model 'it_vectors_wiki_lg' (1.0.1) requires spaCy v2.1 and is incompatible with the current spaCy version (2.3.4). This may lead to unexpected results or runtime errors. To resolve this, download a newer compatible model or retrain your custom model with the current spaCy version. For more details and available updates, run: python -m spacy validate

.../python3.7/site-packages/spacy/_ml.py:287: UserWarning: [W020] Unnamed vectors. This won't allow multiple vectors models to be loaded. (Shape: (962148, 300))

Even though it seems to run smoothly, could you check if the model is running correctly? Or, even better, recreate the model and publish a new release for this spacy version?

Thanks!
Best regards,
Nicola

@MartinoMensio
Copy link
Owner

Hi Nicola!
Thank you for your feedback, I'm happy that someone is using this model :) I will upload a new release soon which will support the latest SpaCy model.
I'm quite sure that both warnings can be ignored, but I will double check and publish the release. I had the same warning with another model and it was working nicely without problems.

Best,
Martino

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

No branches or pull requests

2 participants