Conflicting dependecy requirement bettween spacy(v3.4.4) and spacy-transformer(v1.2.0) #12330
-
We use spacy v3.4.4 with transformer as an extra and have part of custom install using pip with spacy-transformer(v1.2.0) on our sage instance. However when using the pipenv, We can't resolve the dependency since the spacy(v3.4.4) limits the spacy-transformers dependency to <1.2.0. Only spacy(v3.5.0) allows/opens up spacy_transformers to >=1.1.2,<1.3.0. (Our models are trained with spacy v3.4 and spacy-transformer v1.2.0). I am not sure if this purposely or just missed out. Please advise. Please also advise if we can we use spacy v3.4.4 and spacy-transformers v1.2.0 ? Note below setup file conflicts |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
It's intentional that We didn't want Since it might point to a problem on our side: how did you end up with spacy v3.4.4 and spacy-transformers v1.2.0 in the first place?
Due to bug fixes in
(I wouldn't recommend it because of the dependency conflicts, but I don't think there should be any technical problems with using |
Beta Was this translation helpful? Give feedback.
-
Thank you for clarification @adamhadani. |
Beta Was this translation helpful? Give feedback.
It's intentional that
spacy-transformers
v1.2+ is only compatible withspacy
v3.5+. The underlying concern is thatspacy-transformers
v1.2.x models aren't backwards-compatible withspacy-transformers
v1.1.x.We didn't want
pip install spacy[transformers]>=3.4.0,<3.5.0
to potentially install a version ofspacy-transformers
where the saved models aren't compatible with a venv that was installed with the same requirement at an earlier date.Since it might point to a problem on our side: how did you end up with spacy v3.4.4 and spacy-transformers v1.2.0 in the first place?
pip
won't 100% prevent you from installing conflicting packages, but it usually either upgrades/downgrades in the backgro…