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
49
+
in the `__del__` method) still ran deterministically.
50
+
51
+
In case you still want to use it in such a context, you will want to search the
52
+
codebase for `__del__` implementations and call these yourself when you see fit.
53
+
54
+
Another way assure proper cleanup of resources is to factor out GitPython into a
55
+
separate process which can be dropped periodically.
56
+
43
57
### RUNNING TESTS
44
58
45
59
*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.
@@ -59,13 +73,6 @@ For more fine-grained control, you can use `nose`.
59
73
60
74
Please have a look at the [contributions file][contributing].
61
75
62
-
### Live Coding
63
-
64
-
You can watch me fix issues or implement new features [live on Twitch][twitch-channel], or have a look at [past recordings on youtube][youtube-playlist]
65
-
66
-
*[Live on Twitch][twitch-channel] (just follow the channel to be notified when a session starts)
Copy file name to clipboardExpand all lines: doc/source/intro.rst
+16
Original file line number
Diff line number
Diff line change
@@ -59,6 +59,22 @@ script:
59
59
60
60
.. note:: In this case, you have to manually install `GitDB`_ as well. It would be recommended to use the :ref:`git source repository <source-code-label>` in that case.
61
61
62
+
Limitations
63
+
===========
64
+
65
+
Leakage of System Resources
66
+
---------------------------
67
+
68
+
GitPython is not suited for long-running processes (like daemons) as it tends to
69
+
leak system resources. It was written in a time where destructors (as implemented
70
+
in the `__del__` method) still ran deterministically.
71
+
72
+
In case you still want to use it in such a context, you will want to search the
73
+
codebase for `__del__` implementations and call these yourself when you see fit.
74
+
75
+
Another way assure proper cleanup of resources is to factor out GitPython into a
76
+
separate process which can be dropped periodically.
0 commit comments