Skip to content

Copy environment for subprocess execution #208

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

Merged
merged 1 commit into from
Nov 17, 2014

Conversation

electrofelix
Copy link

fixes #207 by ensuring the os.environ is copied before overriding LC_MESSAGES, in a similar manner to master.

Git utilizes multiple environment variables to control various
behaviours. Make sure to set LC_MESSAGES on a copy of the environment
instead of discarding any variables that may be set by the user or
default shell environment such as EDITOR.

Add test to assert that when overriding GIT_EDITOR via os.environ that
the modified value will be picked up by and git commands called.

Git utilizes multiple environment variables to control various
behaviours. Make sure to set LC_MESSAGES on a copy of the environment
instead of discarding any variables that may be set by the user or
default shell environment such as EDITOR.

Add test to assert that when overriding GIT_EDITOR via os.environ that
the modified value will be picked up by and git commands called.
@Byron Byron merged commit 8df6b87 into gitpython-developers:0.3 Nov 17, 2014
@Byron Byron added this to the v0.3.3 milestone Nov 17, 2014
@Byron
Copy link
Member

Byron commented Nov 17, 2014

Thanks a lot ! Sorry for missing this one.
If you don't think waiting for 0.3.3 is going to be suitable for you, I can make an intermediate patch release as well.

@electrofelix
Copy link
Author

Alternatively I can issue a point release for git-upstream to ensure the requirements.txt sets "!=0.3.2" for GitPython. Though I wonder if there are other projects impacted by this?

@Byron
Copy link
Member

Byron commented Nov 18, 2014

Let's not find out ;). I have just pushed a patch release to pypi, which incorporates this fix.
It's 0.3.2.1 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants