`exercism test` does not respect active virtual environment Python

[780Farva]

When running the exercism test command within a pyenv/pipenv virtual environment, the tool invokes python3 -m pytest but does not use the correct Python environment. This results in the error No module named pytest even though pytest is installed in the active environment.

Steps to Reproduce:

1. Create and activate a pyenv/pipenv virtual environment.
2. Install dependencies in the Pipfile (including pytest).
3. Run exercism test to execute the tests for an exercise.

Expected Behavior:

exercism test should automatically use the active Python interpreter from the virtual environment and run the tests without issues, respecting the installed dependencies in that environment.

Actual Behavior:

The tool uses the Python interpreter from the global environment or pyenv's default path, causing it to not find the pytest module installed in the virtual environment.

Environment Details:

• Operating System: Ubuntu via WSL2 on Windows
• Python Version: 3.11.11 (via pyenv)
• exercism Version: 3.5.4
• pytest Version: 8.3.5

[github-actions]

Hello. Thanks for opening an issue on Exercism 🙂

At Exercism we use our Community Forum, not GitHub issues, as the primary place for discussion. That allows maintainers and contributors from across Exercism's ecosystem to discuss your problems/ideas/suggestions without them having to subscribe to hundreds of repositories.

This issue will be automatically closed. Please use this link to copy your GitHub Issue into a new topic on the forum, where we look forward to chatting with you!

If you're interested in learning more about this auto-responder, please read this blog post.

[glennj]

The cli calls this command in a new shell:

python3 -m pytest -o markers=task {{test_files}}

https://github.com/exercism/cli/blob/main/workspace%2Ftest_configurations.go#L214

I don't think exercism test can possibly run in your current shell's environment.

[glennj]

I could suggest ways to write a shell function to work around this, but that would be outside the scope of the cli.

[780Farva]

I think you're right. Thanks for confirming