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
GitPython is not suited for long-running processes (like daemons) as it tends to
48
-
leak system resources. It was written in a time where destructors (as implemented
48
+
leak system resources. It was written in a time where destructors (as implemented
49
49
in the `__del__` method) still ran deterministically.
50
50
51
51
In case you still want to use it in such a context, you will want to search the
@@ -61,7 +61,7 @@ as they are kept alive solely by their users, or not.
61
61
62
62
### RUNNING TESTS
63
63
64
-
*Important*: Right after cloning this repository, please be sure to have executed the `init-tests-after-clone.sh` script in the repository root. Otherwise you will encounter test failures.
64
+
*Important*: Right after cloning this repository, please be sure to have executed the `./init-tests-after-clone.sh` script in the repository root. Otherwise you will encounter test failures.
65
65
66
66
The easiest way to run test is by using [tox](https://pypi.python.org/pypi/tox) a wrapper around virtualenv. It will take care of setting up environnements with the proper dependencies installed and execute test commands. To install it simply:
67
67
@@ -70,8 +70,8 @@ The easiest way to run test is by using [tox](https://pypi.python.org/pypi/tox)
70
70
Then run:
71
71
72
72
tox
73
-
74
-
73
+
74
+
75
75
For more fine-grained control, you can use `nose`.
76
76
77
77
### Contributions
@@ -100,7 +100,7 @@ Please have a look at the [contributions file][contributing].
100
100
* Finally, set the upcoming version in the `VERSION` file, usually be
101
101
incrementing the patch level, and possibly by appending `-dev`. Probably you
0 commit comments