-
Notifications
You must be signed in to change notification settings - Fork 14
Fix/pythonpath #22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix/pythonpath #22
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
Adds a cross-platform setup script to configure PYTHONPATH and generate a VS Code .env file, updates documentation, and integrates the new workflow into VS Code tasks and settings.
- Introduces
setup/setup_python_path.pyto detect the project root, adjustsys.path, and generate a.envfile - Updates both
setup/README.mdand the mainREADME.mdwith usage instructions for the new script - Configures VS Code via
tasks.jsonandsettings.json, and removes legacy entries from.env
Reviewed Changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
| setup/setup_python_path.py | New script for runtime PYTHONPATH setup and .env file generation |
| setup/README.md | Added usage instructions for the setup script |
| README.md | Added a step to run the setup script for environment config |
| .vscode/tasks.json | VS Code task to invoke the setup script |
| .vscode/settings.json | Enabled activateEnvironment and pointed python.envFile to .env |
| .env | Removed outdated relative PYTHONPATH entries |
Comments suppressed due to low confidence (1)
setup/setup_python_path.py:51
- Add unit or integration tests covering both
setup_python_pathandgenerate_env_fileto verify that PYTHONPATH adjustments and .env file generation behave correctly across platforms.
def setup_python_path() -> None:
|
Verified working on Windows as well. Thank you, @anotherRedbeard! |
Resolves #21.