You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Quick Create, error: %ProgramFiles%\Microsoft VS Code Insiders does not appear to be a Python project #1739
... [info] error: C:\Program Files\Microsoft VS Code Insiders does not appear to be a Python project, as neither pyproject.toml nor setup.py are present in the directory
🤖 Triage: the venv is created successfully; the subsequent dependency install fails. Numba’s requirements.txt contains -e ., and although we pass the requirements file as an absolute path, uv resolves . against the install process’s cwd. The log shows it resolving to C:\Program Files\Microsoft VS Code Insiders rather than c:\clones\numba.
Quick Create already knows the project root (venvRoot), and the internal package-command options support cwd, but PackageManagementOptions does not carry it through api.managePackages, and both pip/uv install commands pass undefined for cwd. We should pass the owning project root through package management and use it for installation (with regression coverage for -e . in requirements files under both uv and pip). An environment may be shared or external, so inferring its project solely from the environment path is not reliable.
Activity
eleanorjboyd commentedon Sep 23, 2026
🤖 Triage: the venv is created successfully; the subsequent dependency install fails. Numba’s
requirements.txtcontains-e ., and although we pass the requirements file as an absolute path, uv resolves.against the install process’s cwd. The log shows it resolving toC:\Program Files\Microsoft VS Code Insidersrather thanc:\clones\numba.Quick Create already knows the project root (
venvRoot), and the internal package-command options supportcwd, butPackageManagementOptionsdoes not carry it throughapi.managePackages, and both pip/uv install commands passundefinedfor cwd. We should pass the owning project root through package management and use it for installation (with regression coverage for-e .in requirements files under both uv and pip). An environment may be shared or external, so inferring its project solely from the environment path is not reliable.Eduardo Villalpando Mello (@edvilme) Could you weigh in on the API shape for passing the project working directory to
managePackages?