__init__: don't run refresh on import

Consumers of gitpython may not need to use it in all use cases, and may
want to be able to run (without using gitpython) in environments where
git is not available on PATH. While this can be worked around by setting
the GIT_PYTHON_REFRESH environment variable, adding special handling for
gitpython means that it can't be imported just like everything else in
an import block at the top of the module, and environment variables have
potentially undesired propagation behaviour.

Previously, it was also nontrivial to distinguish gitpython failing to
import because of missing git or because e.g. gitpython isn't installed
at all, because the exception that's raised is an ImportError without
further qualification (except in the error message).

Thus, we now no longer perform `refresh` at the module top level.

Author: lheckemann

doc/source/changes.rst

@@ -2,6 +2,19 @@
 Changelog
 =========
 
+4.0.0
+=====
+
+GitPython will no longer throw an ImportError when no git executable can
+be found at import time. Instead, errors are deferred until the first
+attempt at using it. Consumers with special handling for
+the old ImportError behaviour should instead call `git.refresh` and handle
+GitCommandNotFoundErrors themselves.
+
+See the following for all changes.
+https://github.com/gitpython-developers/GitPython/releases/tag/4.0.0
+
+
 3.1.45
 ======
 

git/__init__.py

@@ -291,10 +291,4 @@ def refresh(path: Optional[PathLike] = None) -> None:
 
     GIT_OK = True
 
-
-try:
-    refresh()
-except Exception as _exc:
-    raise ImportError("Failed to initialize: {0}".format(_exc)) from _exc
-
 # } END initialize git executable path