[Bug]

[bhumitnagda]

Bug Description

On Windows systems, running setup.py fails during dependency installation even though the virtual environment and pip are correctly created. The script attempts to invoke pip directly via a relative path (venv\Scripts\pip), which is not reliably recognized by the Windows shell when executed through subprocess. This causes dependency installation to fail despite pip being present and functional inside the virtual environment.

Steps to Reproduce

1. Clone the PyDex repository on a Windows machine
2. Ensure Python 3.13 is installed and available in PATH
3. Run the setup script: python setup.py
4. Observe the failure during the “Installing dependencies” step

Expected Behavior

The setup script should successfully install dependencies from requirements.txt using the virtual environment’s Python interpreter, without requiring manual activation of the virtual environment.

Actual Behavior

The setup script fails with an error indicating that venv\Scripts\pip is not recognized as a valid command, even though pip exists and works when invoked via python -m pip.

Environment

• OS: Windows 11 (version 10.0.26200)
• Python version: 3.13.0
• PyDex version: Latest

Additional Context

Manually running the following command works correctly, confirming that pip is installed and functional within the virtual environment:

Error Output

❌ Installing dependencies failed!
Error: 'venv\Scripts\pip' is not recognized as an internal or external command,
operable program or batch file.

[bhumitnagda]

I’ve already identified the root cause on Windows and have a solution in mind.
Please assign this issue to me. Thanks!