Skip to content

Python -00 test is fragile to PATH #21450

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

Closed
TomAugspurger opened this issue Jun 12, 2018 · 3 comments
Closed

Python -00 test is fragile to PATH #21450

TomAugspurger opened this issue Jun 12, 2018 · 3 comments
Labels
CI Continuous Integration good first issue Unreliable Test Unit tests that occasionally fail
Milestone

Comments

@TomAugspurger
Copy link
Contributor

subprocess.check_call(["python", "-OO", "-c", "import pandas"])

that assumes that first python on the PATH is the one running the tests, which it may not be (e.g. if doing ./venv/bin/python

We should replace python with something like sys.executable.

@TomAugspurger TomAugspurger added CI Continuous Integration Unreliable Test Unit tests that occasionally fail good first issue Effort Low labels Jun 12, 2018
@WillAyd
Copy link
Member

WillAyd commented Jun 12, 2018

Hmm interesting. Is this causing issues with CI or more of a concern with local configurations?

@TomAugspurger
Copy link
Contributor Author

TomAugspurger commented Jun 12, 2018 via email

@WillAyd
Copy link
Member

WillAyd commented Jun 12, 2018

Probably have a similar issue with the below:

call = ['python', '-c', code]

If possible might be a good idea to set up the executable as a shared fixture

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI Continuous Integration good first issue Unreliable Test Unit tests that occasionally fail
Projects
None yet
Development

No branches or pull requests

3 participants