Graido version Graido/chatbot Space

Spaces
1

I used Graido/chatbot Space template to create my app. But it seems that it is not possible to install the correct version of Gradio. I configured version 5.29.0:

README.md:
...
sdk: gradio
sdk_version: 5.29.0
...

requirements.txt
gradio==5.29.0
huggingface_hub==0.31.1

but after building/running the app I see:

user@r-datenoio-dateno-chatbot-o9ssw0sg-1d555-to0vn:~/app$ python
Python 3.10.17 (main, May  9 2025, 23:45:39) [GCC 12.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import gradio, huggingface_hub
>>> gradio.__version__
'5.0.1'
>>> huggingface_hub.__version__
'0.31.1'

In Building log I see:

--> RUN --mount=target=/tmp/requirements.txt,source=requirements.txt pip install --no-cache-dir -r /tmp/requirements.txt
...

Successfully installed aiofiles-24.1.0 annotated-types-0.7.0 anyio-4.9.0 exceptiongroup-1.2.2 fastapi-0.115.12 ffmpy-0.5.0 gradio-5.29.0 gradio-client-1.10.0 groovy-0.1.2 h11-0.16.0 httpcore-1.0.9 httpx-0.28.1 jinja2-3.1.6 markdown-it-py-3.0.0 markupsafe-3.0.2 mdurl-0.1.2 orjson-3.10.18 pillow-11.2.1 pydantic-2.11.4 pydantic-core-2.33.2 pydub-0.25.1 pygments-2.19.1 python-multipart-0.0.20 rich-14.0.0 ruff-0.11.9 safehttpx-0.1.6 semantic-version-2.10.0 shellingham-1.5.4 sniffio-1.3.1 starlette-0.46.2 tomlkit-0.13.2 typer-0.15.3 typing-inspection-0.4.0 uvicorn-0.34.2 websockets-15.0.1
DONE 7.8s

--> RUN pip install --no-cache-dir      gradio[oauth]==5.0.1    "uvicorn>=0.14.0"       spaces
...
  Attempting uninstall: gradio
    Found existing installation: gradio 5.29.0
    Uninstalling gradio-5.29.0:
      Successfully uninstalled gradio-5.29.0

Successfully installed aiofiles-23.2.1 authlib-1.5.2 cffi-1.17.1 cryptography-44.0.3 gradio-5.0.1 gradio-client-1.4.0 itsdangerous-2.2.0 markupsafe-2.1.5 pillow-10.4.0 psutil-5.9.8 pycparser-2.22 spaces-0.35.0 tomlkit-0.12.0 websockets-12.0

This looks like a forced downgrade scenario for Graido via template’s Dockerfile. Is this the correct behavior?

1 Like
2

It seems to be fine now.

gradio version: 5.29.0
huggingface_hub version: 0.31.1
3

I recreated Space from scratch, unfortunately – the same situation :frowning:

--> RUN --mount=target=/tmp/requirements.txt,source=requirements.txt     pip install --no-cache-dir -r /tmp/requirements.txt
...
Successfully installed aiofiles-24.1.0 annotated-types-0.7.0 anyio-4.9.0 exceptiongroup-1.2.2 fastapi-0.115.12 ffmpy-0.5.0 gradio-5.29.0 gradio-client-1.10.0 groovy-0.1.2 h11-0.16.0 httpcore-1.0.9 httpx-0.28.1 jinja2-3.1.6 markdown-it-py-3.0.0 markupsafe-3.0.2 mdurl-0.1.2 orjson-3.10.18 pillow-11.2.1 pydantic-2.11.4 pydantic-core-2.33.2 pydub-0.25.1 pygments-2.19.1 python-multipart-0.0.20 rich-14.0.0 ruff-0.11.9 safehttpx-0.1.6 semantic-version-2.10.0 shellingham-1.5.4 sniffio-1.3.1 starlette-0.46.2 tomlkit-0.13.2 typer-0.15.3 typing-inspection-0.4.0 uvicorn-0.34.2 websockets-15.0.1
DONE 7.9s

--> RUN pip install --no-cache-dir      gradio[oauth]==5.0.1    "uvicorn>=0.14.0"       spaces
Collecting gradio==5.0.1 (from gradio[oauth]==5.0.1)
  Downloading gradio-5.0.1-py3-none-any.whl.metadata (15 kB)
...
  Attempting uninstall: gradio-client
    Found existing installation: gradio_client 1.10.0
    Uninstalling gradio_client-1.10.0:
      Successfully uninstalled gradio_client-1.10.0
  Attempting uninstall: gradio
    Found existing installation: gradio 5.29.0
    Uninstalling gradio-5.29.0:
      Successfully uninstalled gradio-5.29.0

Successfully installed aiofiles-23.2.1 authlib-1.5.2 cffi-1.17.1 cryptography-44.0.3 gradio-5.0.1 gradio-client-1.4.0 itsdangerous-2.2.0 markupsafe-2.1.5 pillow-10.4.0 psutil-5.9.8 pycparser-2.22 spaces-0.35.0 tomlkit-0.12.0 websockets-12.0
...
1 Like
4

Today I created Gradio Space again (Test - a Hugging Face Space by datenoio) – the problem still exists.

Steps to reproduce:

  1. Create new space:
    Space SDK: Gradio
    Gradio template: chatbot
    Space hardware: CPU basic · 2 vCPU · 16 GB · FREE
    Enable dev mode
    Public
  2. Change Gradio’s version (patch).
  3. Space settings – Factory rebuild (build log).
  4. Check Gradio’s version on Space SSH session:
user@r-datenoio-test-n8tjolp9-e4272-hlpmp:~/app$ cat requirements.txt
gradio==5.29.0
huggingface_hub==0.31.1

user@r-datenoio-test-n8tjolp9-e4272-hlpmp:~/app$ cat README.md
---
title: Test
emoji: 💬
colorFrom: yellow
colorTo: purple
sdk: gradio
sdk_version: 5.29.0
app_file: app.py
pinned: false
---

An example chatbot using [Gradio](https://gradio.app), [`huggingface_hub`](https://huggingface.co/docs/huggingface_hub/v0.22.2/en/index), and the [Hugging Face Inference API](https://huggingface.co/docs/api-inference/index).
user@r-datenoio-test-n8tjolp9-e4272-hlpmp:~/app$ python
Python 3.10.17 (main, May  9 2025, 23:45:39) [GCC 12.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import gradio, huggingface_hub
>>> gradio.__version__
'5.0.1'
>>> huggingface_hub.__version__
'0.31.1'
>>>
1 Like
5

Hmm… When using Dev mode, there are sometimes git inconsistencies, but I think that’s what it is.:thinking:

6

Yep! It looks like black magic: after switching off dev mode, Gradio’s version upgraded to 5.29.0, and after switching on dev mode again, the app still works with 5.29.0 :zany_face:

1 Like