Skip to content

armgit / cua

Public Imported from GitHub
0

Scale computer-use 2.0 with open-source drivers, cross-OS sandboxes, and benchmarks for training, evaluation, and data generation.

Don't create .env for VS Code

James Murdza4a00635e174a
diff --git a/scripts/build-uv.sh b/scripts/build-uv.sh
index 7d8c2e5de5..487385dd74 100755
--- a/scripts/build-uv.sh
+++ b/scripts/build-uv.sh
@@ -160,10 +160,6 @@ install_package "libs/python/mcp-server" "mcp-server"
print_step "Installing development dependencies with UV..."
uv pip install -e ".[dev,test,docs]"
-# Create a .env file for VS Code to use the virtual environment
-print_step "Creating .env file for VS Code..."
-echo "PYTHONPATH=${PROJECT_ROOT}/libs/python/core:${PROJECT_ROOT}/libs/python/computer:${PROJECT_ROOT}/libs/python/agent:${PROJECT_ROOT}/libs/python/som:${PROJECT_ROOT}/libs/python/pylume:${PROJECT_ROOT}/libs/python/computer-server:${PROJECT_ROOT}/libs/python/mcp-server" > .env
-
print_success "All packages installed successfully with UV!"
print_step "Your virtual environment is ready. To activate it:"
echo " source .venv/bin/activate"