fix: Ensure uv installs packages in virtual environment #19
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
September 2, 2025 15:09
The setup-venv.js script was installing Python packages to the global uv environment instead of the project's virtual environment. This caused the API server to fail with "No module named uvicorn" error. - Added --python .venv/bin/python flag to uv pip install command - Updated error message to include the correct command syntax This ensures all Python dependencies are properly installed in the project's isolated virtual environment.
- Added dev-docs/ to the .gitignore file to prevent tracking of development documentation files.
|
Confirmed this fixed my setup. Thanks! 🙇 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes API server startup failure caused by Python packages not being installed in the virtual environment.
Problem
The
setup-venv.jsscript was usinguv pip install -r requirements.txtwithout specifying the target virtual environment. This caused packages to be installed in the global uv environment instead of the project's.venv, leading to "No module named uvicorn" errors when starting the API server.Solution
--python .venv/bin/pythonflag to theuv pip installcommandTest plan
npm run ensure:venvThis ensures all Python dependencies are properly installed in the project's isolated virtual environment.