Skip to content

Comments

Add cross-platform Python interpreter path for VS Code#13

Merged
pmalarme merged 4 commits intofeature/add-documentation-and-copilot-instructionsfrom
copilot/sub-pr-9-again
Feb 17, 2026
Merged

Add cross-platform Python interpreter path for VS Code#13
pmalarme merged 4 commits intofeature/add-documentation-and-copilot-instructionsfrom
copilot/sub-pr-9-again

Conversation

Copy link
Contributor

Copilot AI commented Feb 17, 2026

Summary

Updated python.defaultInterpreterPath in .vscode/settings.json to use a cross-platform path that works on both Windows and POSIX systems. The setting "${workspaceFolder}/.venv" allows VS Code to automatically resolve to the correct platform-specific interpreter:

  • Windows: .venv/Scripts/python.exe
  • macOS/Linux: .venv/bin/python

Testing

  • Not run (configuration-only change, no code modified)

Checklist

  • Linked issue or task reference
  • Added/updated tests where relevant
  • Updated docs/README if needed
  • No secrets or sensitive data added
  • Considered backward compatibility and deployment impact

Additional context


💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

…settings

Co-authored-by: pmalarme <686568+pmalarme@users.noreply.github.com>
Copilot AI changed the title [WIP] Update documentation and copilot instructions based on feedback Remove Unix-specific Python interpreter path from VS Code settings Feb 17, 2026
Copilot AI requested a review from pmalarme February 17, 2026 14:20
@pmalarme
Copy link
Owner

@copilot can we create a setting that is ok for both Windows and POSIX machines?

Co-authored-by: pmalarme <686568+pmalarme@users.noreply.github.com>
Copy link
Contributor Author

Copilot AI commented Feb 17, 2026

@copilot can we create a setting that is ok for both Windows and POSIX machines?

Yes! Added cross-platform setting in commit 88f3e90. Using "${workspaceFolder}/.venv" allows VS Code to automatically resolve to the correct interpreter path for each platform:

  • Windows: .venv/Scripts/python.exe
  • macOS/Linux: .venv/bin/python

Copilot AI changed the title Remove Unix-specific Python interpreter path from VS Code settings Add cross-platform Python interpreter path for VS Code Feb 17, 2026
@pmalarme pmalarme marked this pull request as ready for review February 17, 2026 14:33
Copilot AI review requested due to automatic review settings February 17, 2026 14:33
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the VS Code workspace configuration to change how the Python interpreter is selected for this repository’s .venv-based development workflow.

Changes:

  • Changes python.defaultInterpreterPath in .vscode/settings.json from an explicit POSIX interpreter path (.venv/bin/python) to ${workspaceFolder}/.venv.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
@pmalarme pmalarme merged commit e06e7be into feature/add-documentation-and-copilot-instructions Feb 17, 2026
@pmalarme pmalarme deleted the copilot/sub-pr-9-again branch February 17, 2026 14:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants