We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
on the most distros it points to py2 or it is not really deterministic.
The call itself is following: fp.write('COMP_WORDBREAKS="$COMP_WORDBREAKS" python -m pytest 8>&1 9>&2')
fp.write('COMP_WORDBREAKS="$COMP_WORDBREAKS" python -m pytest 8>&1 9>&2')
I suppose it should use sys.executable or at least python3 as the py2 is not compatible anyway.
sys.executable
python3
The text was updated successfully, but these errors were encountered:
sys.executable would be best, would you like to submit a patch? thanks!
(it mostly works right now because it runs in a virtualenv)
Sorry, something went wrong.
Do not call python directly but use sys.executable. Fixes #5872 (#5873)
7c64d5d
Do not call python directly but use sys.executable. Fixes #5872
Successfully merging a pull request may close this issue.
on the most distros it points to py2 or it is not really deterministic.
The call itself is following:
fp.write('COMP_WORDBREAKS="$COMP_WORDBREAKS" python -m pytest 8>&1 9>&2')
I suppose it should use
sys.executable
or at leastpython3
as the py2 is not compatible anyway.The text was updated successfully, but these errors were encountered: