-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove environment mangling #2132
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is interesting as on the face of it we seem to simply be copying the os.environ
so I wouldn't have expected any difference between this and the new code where we use the os.environ
directly. I imagine the reason this was do was to create a copy of the environment to avoid polluting it.
execute('source {0} {1}'.format(setup, " ".join(setup_args)), shell=True, env=self.env, update_env=True) | ||
|
||
else: | ||
# bug #44334: Ganga/Utility/Shell.py does not save environ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I assume that the bug #44334
is a reference to something very old that we don't care about.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Both GangaDirac
and GangaLHCb
tests are failing. The GangaDirac
failures seems directly caused by the changes here. The GangaLHCb
ones are hard to understand but might just be caused by the Dirac
failures.
Fixes #2104
We should leave the environments as
os._Environ
objects. It stop the mangling of the environment that causes #2104