AppWorld Integration Environment Conflicts #297
Description
#235 integrated AppWorld with rLLM; however, there is currently no documentation on how to set up the environment. When I tried to prepare the AppWorld environment using the official AppWorld documentation, I found that many AppWorld packages are not compatible with rLLM. Could @sunan135 please provide documentation on how to set up the AppWorld environment in rLLM so that we can run the example you provided? Thank you!
Reproduction
- Install rLLM (fresh venv/conda).
- Install AppWorld as documented:
pip install appworld appworld install appworld download data
- Run the example:
python -m examples.appworld.run_appworld_agent
Error
python -m examples.appworld.run_appworld_agent
Traceback (most recent call last):
File "/opt/conda/envs/ptca/lib/python3.10/runpy.py", line 196, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/opt/conda/envs/ptca/lib/python3.10/runpy.py", line 86, in _run_code
exec(code, run_globals)
File "rllm/examples/appworld/run_appworld_agent.py", line 9, in <module>
from rllm.environments.appworld.appworld_env import AppWorldEnv
File "rllm/rllm/environments/appworld/appworld_env.py", line 5, in <module>
from appworld import AppWorld as _AppWorld
File "/opt/conda/envs/ptca/lib/python3.10/site-packages/appworld/__init__.py", line 4, in <module>
from appworld.environment import AppWorld
File "/opt/conda/envs/ptca/lib/python3.10/site-packages/appworld/environment.py", line 10, in <module>
from typing import Any, ClassVar, Literal, Self
ImportError: cannot import name 'Self' from 'typing' (/opt/conda/envs/ptca/lib/python3.10/typing.py)
Environment Conflicts
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
appworld 0.1.3 requires fastapi<0.111.0,>=0.110.0, but you have fastapi 0.121.0 which is incompatible.
appworld 0.1.3 requires httpx<0.28.0,>=0.27.0, but you have httpx 0.28.1 which is incompatible.
appworld 0.1.3 requires pydantic<2.0.0,>=1.9.0, but you have pydantic 2.11.10 which is incompatible.
appworld 0.1.3 requires python-multipart<0.0.10,>=0.0.9, but you have python-multipart 0.0.20 which is incompatible.
appworld 0.1.3 requires rich<14.0.0,>=13.7.1, but you have rich 14.2.0 which is incompatible.
appworld 0.1.3 requires typer<0.13.0,>=0.12.3, but you have typer 0.19.2 which is incompatible.
appworld 0.1.3 requires uvicorn<0.28.0,>=0.27.1, but you have uvicorn 0.38.0 which is incompatible.
azureml-inference-server-http 1.4.0 requires pydantic~=2.9.0, but you have pydantic 2.11.10 which is incompatible.
fastapi-login 1.9.3 requires anyio[trio]<4.0.0,>=3.6.2, but you have anyio 4.11.0 which is incompatible.
opentelemetry-exporter-otlp-proto-grpc 1.26.0 requires opentelemetry-sdk~=1.26.0, but you have opentelemetry-sdk 1.38.0 which is incompatible.
opentelemetry-exporter-otlp-proto-http 1.26.0 requires opentelemetry-sdk~=1.26.0, but you have opentelemetry-sdk 1.38.0 which is incompatible.
opentelemetry-proto 1.26.0 requires protobuf<5.0,>=3.19, but you have protobuf 5.29.5 which is incompatible.
sqlmodel 0.0.10 requires pydantic<2.0.0,>=1.9.0, but you have pydantic 2.11.10 which is incompatible.
verl 0.5.0 requires numpy<2.0.0, but you have numpy 2.2.6 which is incompatible.
verl 0.5.0 requires tensordict!=0.9.0,<=0.9.1,>=0.8.0, but you have tensordict 0.6.2 which is incompatible.
vllm 0.8.5.post1 requires opentelemetry-api<1.27.0,>=1.26.0, but you have opentelemetry-api 1.38.0 which is incompatible.
vllm 0.8.5.post1 requires opentelemetry-sdk<1.27.0,>=1.26.0, but you have opentelemetry-sdk 1.38.0 which is incompatible.