gradio lower bound differs between pyproject.toml and requirements.txt

Summary

The Gradio lower bound differs between pyproject.toml and requirements.txt:

• pyproject.toml: gradio>=6.4.0
• requirements.txt: gradio>=3.50.2

Reporter-assessed priority: P2/P3 because this is an installation consistency issue rather than a confirmed crash in every environment. Maintainers should adjust the priority as appropriate.

Environment

• Repository: camel-ai/owl
• Commit reviewed: 9dbcf271a889f04e23894cc928069617b4483815
• Files:
  • pyproject.toml
  • requirements.txt

Evidence

pyproject.toml:

"gradio>=6.4.0"

requirements.txt:

gradio>=3.50.2

These appear to be two supported installation paths, but they allow different minimum Gradio versions.

Why This Matters

Users installing from requirements.txt can end up with an older Gradio version if their environment already has one installed, if another constraint pins it, or if a lockfile is generated from the looser requirement.

That can lead to behavior that differs from pip install -e ., where pyproject.toml requires gradio>=6.4.0.

Expected Behavior

Both installation paths should express the same minimum supported Gradio version.

Actual Behavior

The two dependency files currently disagree on the minimum Gradio version.

Suggested Fix

Align requirements.txt with pyproject.toml, or clarify that requirements.txt is intentionally broader.

For example:

gradio>=6.4.0

中文补充

pyproject.toml 和 requirements.txt 对 Gradio 的最低版本要求不一致。用户通过不同安装路径可能得到不同的依赖环境，建议统一最低版本，减少 Web UI 相关问题的排查成本。