-
Notifications
You must be signed in to change notification settings - Fork 224
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Question] running pytest-xdist
in a read-only system
#1006
Comments
dtcMLOps
changed the title
[Question] running pytest-xdist in a read-only system
[Question] running Jan 18, 2024
pytest-xdist
in a read-only system
i believe the PYTHONDONTWRITEBYTECODE env var should pass over to popen subprocesses execnet has a flag for passing -B to python to ensure no bytecode is written but its not exposed easily for xdist |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 runningpytest
with:PYTHONDONTWRITEBYTECODE=1
andsys.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 thepytest-xdist
plugin.Do you know if there is a way to tell
pytest-xdist
no to generate the__pycache__
directory?Aditional context
The text was updated successfully, but these errors were encountered: