Tests assume a specific interpreter name

[Ben Finney]

The test cases attempt to invoke the Python interpreter in a sub-process. The assumption is that the command python will invoke the Python interpreter. This assumption is not universally true, and causes the test cases to fail when the correct Python interpreter does not have that name.

Instead, the current Python interpreter program file path should be interrogated from the sys.executable attribute.

[Ben Finney]

I have implemented changes to address this bug, in the ‘wip/issue/use-current-interpreter-name’ branch of my personal fork repository. The branch currently merges cleanly to ‘master’.

[Steven Tobin]

Hey, thanks for the fix - in the latest release and newest tag

[Ben Finney]

Thanks, I'm glad to contribute.