pytest-dev / pytest-dev/pytest-xdist
[Question] running `pytest-xdist` in a read-only system
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.9k
- Forks
- 287
- Avg merge
- 9h 30m
- Merged PRs (30d)
- 2
Description
Hi team,
Greetings.
I have a question regarding the plugin when running in a read-only system like Databricks job clusters. I have disabled __pycache__ creation when running pytest with:
PYTHONDONTWRITEBYTECODE=1 and sys.dont_write_bytecode = True.
The tests were running successfully, but when I tried to enable the pytest-xdist plugin support with the -n logical or -n auto argument, pytest is creating the __pycache__ directory again and my run failed. I am guessing this is related to the pytest-xdist plugin.
Do you know if there is a way to tell pytest-xdist no to generate the __pycache__ directory?
Aditional context
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 reproducing the read-only run with PYTHONDONTWRITEBYTECODE=1 and sys.dont_write_bytecode = True, then compare pytest-xdist with -n logical and -n auto. Determine whether pycache creation comes from pytest-xdist and document whether a configuration or workaround prevents it.
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
- Needs clarification
- Newbie friendliness
- 25/100