summaryrefslogtreecommitdiff
path: root/TODO
diff options
context:
space:
mode:
authorSebastian Thiel <byronimo@gmail.com>2009-11-05 20:09:35 +0100
committerSebastian Thiel <byronimo@gmail.com>2009-11-05 20:09:35 +0100
commit46c9a0df4403266a320059eaa66e7dce7b3d9ac4 (patch)
tree7829c074049295b869db1bdcf4f457ebefea62b7 /TODO
parenta67bf61b5017e41740e997147dc88282b09c6f86 (diff)
downloadgitpython-46c9a0df4403266a320059eaa66e7dce7b3d9ac4.tar.gz
cmd: added clear_cache method now used by test repo decorators to be sure persistent commands are killed before trying to remove the directory. Unfortunately, it still claims someone has opened the file. handle.exe does not show anyone, so what is happening here ? Is it just a windows odity ? If nothing helps I could just keep the temp data, but lets do some more testing first
Diffstat (limited to 'TODO')
-rw-r--r--TODO10
1 files changed, 7 insertions, 3 deletions
diff --git a/TODO b/TODO
index 15847102..d5971f2d 100644
--- a/TODO
+++ b/TODO
@@ -11,9 +11,13 @@ General
a sha or ref unless cat-file is used where it must be a sha
* Overhaul command caching - currently its possible to create many instances of
the std-in command types, as it appears they are not killed when the repo gets
- deleted. A clear() method could already help to allow long-running programs
- to remove cached commands after an idle time.
-
+ deleted.
+* git command on windows may be killed using the /F options which probably is like
+ SIGKILL. This is bad as the process might be doing something, leaving the resource
+ locked and/or in an inconsistent state. Without the /F option, git does not terminate
+ itself, probably it listens to SIGINT which is not sent by TASKKILL. We can't really
+ help it, but may be at some point git handles windows signals properly.
+
Object
------
* DataStream method should read the data itself. This would be easy once you have