@kenr thanks a lot for the PR.
However, are you sure about this implementation? the issue is that you are changing the parent env and not the child process.
ya the child process will get the same env, meaning it will also have it, but it will impact the parent process which feels a bit unexpected.
most child process apis have an ability to provide a new env and rust isn't different here.
for example you can do:

Command::new("ls")
        .env("PATH", "/bin")
        .spawn()
        .expect("ls command failed to start");

that way, only the child process will have those env vars and parent process is not affected at all.
wdyt?

Codecov Report

Merging #16 (642c049) into master (a7bce2b) will increase coverage by 1.26%.
The diff coverage is 100.00%.

❗ Current head 642c049 differs from pull request most recent head d6a122e. Consider uploading reports for the commit d6a122e to get more accurate results

@@            Coverage Diff             @@
##           master      #16      +/-   ##
==========================================
+ Coverage   92.40%   93.67%   +1.26%     
==========================================
  Files           6        6              
  Lines         395      411      +16     
==========================================
+ Hits          365      385      +20     
+ Misses         30       26       -4     

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a7bce2b...d6a122e. Read the comment docs.

@sagiegurari I agree with you, the parent should not be polluted with the environment variables in options.
I've updated the PR with a fix and test covering this.

excellent work!!! thanks a lot.