Fix environment not set correctly for Windows subprocess backend #335
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a follow-up on #327; not sure exactly why it didn't come up then, but maybe because I now have a UNC path as my working directory; cmd rejects this and defaults to C:\Windows. But the working directory shouldn't matter anyway.
I was getting this error:
which apparently can happen when trying to invoke python using
Popen
if the environment isn't set correctly: https://stackoverflow.com/a/72845540I realized that I was adding semicolons to the end of each
SET
line in the .bat file, which I believe was setting the variables to incorrect values. Deleting the semicolon fixed this for me.