Spaces:
Running on Zero
Running on Zero
Let the Space builder own torch/gradio/spaces
Browse filesThe builder already installs torch (pinned <=2.11.0), gradio, uvicorn and
spaces. Pinning a CPU-only torch from a custom index here collided with that
pin and failed the build outright.
- requirements.txt +3 -5
requirements.txt
CHANGED
|
@@ -1,8 +1,6 @@
|
|
| 1 |
-
|
| 2 |
-
|
| 3 |
-
|
| 4 |
-
torch
|
| 5 |
transformers>=4.44,<5
|
| 6 |
sentencepiece
|
| 7 |
sacremoses
|
| 8 |
-
numpy
|
|
|
|
| 1 |
+
# torch, gradio, uvicorn and spaces are installed by the Space builder itself
|
| 2 |
+
# (and torch is pinned there) — declaring them here only creates a resolver
|
| 3 |
+
# conflict, which is what failed the first build.
|
|
|
|
| 4 |
transformers>=4.44,<5
|
| 5 |
sentencepiece
|
| 6 |
sacremoses
|
|
|