Describe the bug
When I do session.run("stuff", env={}), I would expect to run the command in an environment where no variable is defined, however a copy of the local environment is made. Similarly, if I do session.run("stuff", env={"CREEPY": "TRUE"}) I would expect to run in an environment where only $CREEPY is defined, while this only updates the copy of the current environment.
How to reproduce
Check the environment when running with env={}.
Expected behavior
If I pass env={}, I would expect to work in a clean environment. At the moment, the workaround is to do for instance session.virtualenv.env = {"SYSTEMROOT": os.getenv("SYSTEMROOT", "")} at the beginning of each session, but I find that a bit too cumbersome.
Describe the bug
When I do
session.run("stuff", env={}), I would expect to run the command in an environment where no variable is defined, however a copy of the local environment is made. Similarly, if I dosession.run("stuff", env={"CREEPY": "TRUE"})I would expect to run in an environment where only$CREEPYis defined, while this only updates the copy of the current environment.How to reproduce
Check the environment when running with
env={}.Expected behavior
If I pass
env={}, I would expect to work in a clean environment. At the moment, the workaround is to do for instancesession.virtualenv.env = {"SYSTEMROOT": os.getenv("SYSTEMROOT", "")}at the beginning of each session, but I find that a bit too cumbersome.