Skip to content

Use configured Python interpreter for Metaflow commands (Issue #3)#19

Open
tejeshvenkat wants to merge 1 commit intoouterbounds:mainfrom
tejeshvenkat:feat/python-interpreter-detection
Open

Use configured Python interpreter for Metaflow commands (Issue #3)#19
tejeshvenkat wants to merge 1 commit intoouterbounds:mainfrom
tejeshvenkat:feat/python-interpreter-detection

Conversation

@tejeshvenkat
Copy link
Copy Markdown

Summary

Fixes #3 — The extension now uses the Python interpreter selected in VS Code instead of always using python from PATH.

Changes

  • Read python.defaultInterpreterPath from the Python extension's configuration
  • Fallback to python when no interpreter is configured
  • Quote paths containing spaces for Windows compatibility (e.g., C:\Program Files\Python\python.exe)

Testing

  • Verified with Python extension + venv interpreter selected
  • Verified fallback when no interpreter is set
  • Tested on Windows with paths containing spaces

…ounds#3)

- Read python.defaultInterpreterPath from Python extension config
- Fallback to 'python' from PATH when no interpreter is set
- Quote paths with spaces for Windows compatibility

Made-with: Cursor
@tejeshvenkat tejeshvenkat force-pushed the feat/python-interpreter-detection branch from fbf641a to f8cb74b Compare March 8, 2026 09:54
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.

Support detection of the active Python interpreter from VS Code instead of using hardcoded python

1 participant