Skip to content

Conversation

@moriyoshi
Copy link
Contributor

  • It currently relies on the behavior of subprocess.check_call() that searches for the executable in the search path. Because of it, the test run needs a valid search path setup.

Copy link
Member

@pitrou pitrou left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks reasonable to me. Are there other places in the test suite using the same pattern?

Copy link
Member

@wesm wesm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1. This is the only place I can see where Python itself is being invoked in the test suite

@wesm wesm closed this in 8d78376 Jan 30, 2018
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.

3 participants