posit-dev / posit-dev/mcp-repl
Make interpreter selection easier and more configurable
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 70
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Selecting the Python interpreter should be easier.
mcp-repl should expose an environment variable for choosing the Python interpreter explicitly, for example MCP_REPL_PYTHON, consulted at launch. That should make it easier to use mcp-repl with other environment managers such as pixi or conda.
It would also help to expose interpreter search paths in a future configuration layer, so users can add default locations to search instead of relying only on .venv/bin/python.
Relatedly, --interpreter should be able to accept an absolute path to an R or Python executable, not only the literal r or python backend names.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how mcp-repl selects interpreters at launch and how the --interpreter argument is handled; the issue names no files or tests. Compare the requested environment variable, absolute executable paths, and configurable search paths, then verify that Python and R interpreter selection works with those inputs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, r, rust
- Domain
- cli, developer-experience
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100