pytest-dev / pytest-dev/pytest
ModuleNotFoundError when pytest not in venv
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 14.5k
- Forks
- 3.4k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 35
Description
If pytest is installed system-wide but not in a venv, pytest will run but not find the dependencies installed in the venv. It would be nice if pytest would trigger a descriptive error if the ENV var VIRTUAL_ENV is set but pytest is not running from inside this venv.
pytest 7.2.1 from Debian bookworm (12)
Reproduce:
- Ensure pytest is installed system-wide
- Create venv
- Activate venv and install any module (e.g. foo) not present in system (but not pytest)
- Create a test file importing this module
- Run pytest, it will produce "E ModuleNotFoundError: No module named 'foo'"
Contributor guide
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
Reproduce the reported setup: install pytest system-wide, create and activate a virtual environment, install a module only there, and run a test that imports it. Start by tracing pytest's invocation and environment handling; done means this mismatch produces a descriptive error when VIRTUAL_ENV is set and pytest is outside that environment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100