You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Try to install a recent build of Gradio 4.26.x on Linux, in a requirements file, alongside Spacy. e.g.
gradio>=4.26.0
spacy>=3.0.0
it just wont do it easily with lots of complaints and sits there forever trying version after version:
Your Environment
Operating System: Ubuntu 22.04.4
Python Version Used: 3.11.9
spaCy Version Used: any from 3.x.x upwards
Environment Information: a conda Python environment using Gradio of any recent build.
Here is an example of the most recent version of Gradio being installed, however I tried many other earlier versions of Gradio, I just didnt keep the error messages. You can see PIP just hunts and hunts trying to find a match, which takes a long long time, esp if you keep having to wipe the gradio and try earlier versions.
I tried things a lot of ways around e.g. pip install "spacy==3.5.3" "gradio==4.31.4" or `pip install "spacy>=3.5.3" "gradio>=4.00.0" etc. Which took a long long time.
The reason I am coming to you about this, is because the most restrictive requirements of all packages are within Spacy and you may be willing to validate other versions of typer to work with the new dev build. Not sure how possible that is, I appreciate changing the version of something can lead to development hell and version matching with PIP being a pain.
conflict is caused by:
gradio 4.31.5 depends on typer<1.0 and >=0.12; sys_platform != "emscripten"
spacy 3.7.2 depends on typer<0.10.0 and >=0.3.0
gradio 4.31.5 depends on typer<1.0 and >=0.12; sys_platform != "emscripten"
spacy 3.7.4 depends on typer<0.10.0 and >=0.3.0
gradio 4.31.5 depends on typer<1.0 and >=0.12; sys_platform != "emscripten"
spacy 3.7.1 depends on typer<0.10.0 and >=0.3.0
gradio 4.31.5 depends on typer<1.0 and >=0.12; sys_platform != "emscripten"
spacy 3.7.0 depends on typer<0.10.0 and >=0.3.0
gradio 4.31.5 depends on typer<1.0 and >=0.12; sys_platform != "emscripten"
spacy 3.6.1 depends on typer<0.10.0 and >=0.3.0
gradio 4.31.5 depends on pydantic>=2.0
spacy 3.6.0 depends on pydantic!=1.8, !=1.8.1, <1.11.0 and >=1.7.4
gradio 4.31.5 depends on pydantic>=2.0
spacy 3.5.4 depends on pydantic!=1.8, !=1.8.1, <1.11.0 and >=1.7.4
gradio 4.31.5 depends on typer<1.0 and >=0.12; sys_platform != "emscripten"
spacy 3.5.3 depends on typer<0.8.0 and >=0.3.0
gradio 4.31.5 depends on typer<1.0 and >=0.12; sys_platform != "emscripten"
spacy 3.5.2 depends on typer<0.8.0 and >=0.3.0
gradio 4.31.5 depends on typer<1.0 and >=0.12; sys_platform != "emscripten"
spacy 3.5.1 depends on typer<0.8.0 and >=0.3.0
gradio 4.31.5 depends on typer<1.0 and >=0.12; sys_platform != "emscripten"
spacy 3.5.0 depends on typer<0.8.0 and >=0.3.0
gradio 4.31.5 depends on typer<1.0 and >=0.12; sys_platform != "emscripten"
spacy 3.4.4 depends on typer<0.8.0 and >=0.3.0
gradio 4.31.5 depends on typer<1.0 and >=0.12; sys_platform != "emscripten"
spacy 3.4.3 depends on typer<0.8.0 and >=0.3.0
gradio 4.31.5 depends on typer<1.0 and >=0.12; sys_platform != "emscripten"
spacy 3.4.2 depends on typer<0.5.0 and >=0.3.0
gradio 4.31.5 depends on typer<1.0 and >=0.12; sys_platform != "emscripten"
spacy 3.4.1 depends on typer<0.5.0 and >=0.3.0
```
Thanks
The text was updated successfully, but these errors were encountered:
How to reproduce the behaviour
Try to install a recent build of Gradio 4.26.x on Linux, in a requirements file, alongside Spacy. e.g.
gradio>=4.26.0
spacy>=3.0.0
it just wont do it easily with lots of complaints and sits there forever trying version after version:
Your Environment
Here is an example of the most recent version of Gradio being installed, however I tried many other earlier versions of Gradio, I just didnt keep the error messages. You can see PIP just hunts and hunts trying to find a match, which takes a long long time, esp if you keep having to wipe the gradio and try earlier versions.
I tried things a lot of ways around e.g.
pip install "spacy==3.5.3" "gradio==4.31.4"
or `pip install "spacy>=3.5.3" "gradio>=4.00.0" etc. Which took a long long time.The reason I am coming to you about this, is because the most restrictive requirements of all packages are within Spacy and you may be willing to validate other versions of
typer
to work with the new dev build. Not sure how possible that is, I appreciate changing the version of something can lead to development hell and version matching with PIP being a pain.The text was updated successfully, but these errors were encountered: