Skip to content
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

Use the same python binary to run testimport.py #565

Merged
merged 1 commit into from Oct 17, 2020

Conversation

stefanor
Copy link
Contributor

@stefanor stefanor commented Oct 16, 2020

Rather than relying on the shebang of testimport.py (which will load the first python3 on PATH), use the same binary that the test suite is running under.

On Debian, multiple versions of cPython can be installed concurrently and this lets us test under a non-default version, e.g.:

$ python3.9 -m pytest beancount/

Debian Bug: https://bugs.debian.org/972328

Rather than relying on the shebang of testimport (which will load the
first python3 on PATH), use the same binary that the test suite is
running under.

On Debian, multiple versions of cPython can be installed concurrently
and this lets us test under a non-default version, e.g.:

$ python3.9 -m pytest beancount/
@blais blais merged commit 40a7938 into beancount:master Oct 17, 2020
@stefanor stefanor deleted the test-with-arbitrary-python branch October 17, 2020 20:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants