You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On import git GitPython calls git 2 times, upon running refresh method.
Those calls have potential of being a bug source since the user has no way of providing environmental variables for git. For example, if the user decides to provide the PATH variable for any method utilizing the env variable (eg clone_from), he/she might end up using different git than has been used during import.
The text was updated successfully, but these errors were encountered:
Absolutely true, it is impossible to control the environment for these git calls.
A potential workaround for this case would be to configure the environment of the python process to be the 'best fit for most cases', even though this might still not be enough.
Maybe it's possible to alter the python global env dict prior to importing GitPython, too.
On
import git
GitPython callsgit
2 times, upon running refresh method.Those calls have potential of being a bug source since the user has no way of providing environmental variables for git. For example, if the user decides to provide the
PATH
variable for any method utilizing theenv
variable (egclone_from
), he/she might end up using different git than has been used during import.The text was updated successfully, but these errors were encountered: