diff options
| author | Sebastian Thiel <byronimo@gmail.com> | 2009-10-22 11:04:30 +0200 |
|---|---|---|
| committer | Sebastian Thiel <byronimo@gmail.com> | 2009-10-22 11:04:30 +0200 |
| commit | 33fa178eeb7bf519f5fff118ebc8e27e76098363 (patch) | |
| tree | ab4e5789aa334688d71504d532312fb4ce572b71 /TODO | |
| parent | 3c9f55dd8e6697ab2f9eaf384315abd4cbefad38 (diff) | |
| download | gitpython-33fa178eeb7bf519f5fff118ebc8e27e76098363.tar.gz | |
added Object.data_stream property allowing to stream object data directly.Considering the implementation of the git commnd which temporarily keeps it in a cache, it doesnt make a huge diffence as the data is kept in memory while streaming. Only good thing is that it is in a different process so python will never see it if done properly
Diffstat (limited to 'TODO')
| -rw-r--r-- | TODO | 12 |
1 files changed, 12 insertions, 0 deletions
@@ -15,6 +15,18 @@ General * References should be parsed 'manually' to get around command invocation, but be sure to be able to read packed refs. +Object +------ +* DataStream method should read the data itself. This would be easy once you have + the actul loose object, but will be hard if it is in a pack. In a distant future, + we might be able to do that or at least implement direct object reading for loose + objects ( to safe a command call ). Currently object information comes from + persistent commands anyway, so the penalty is not that high. The data_stream + though is not based on persistent commands. + It would be good to improve things there as cat-file keeps all the data in a buffer + before it writes it. Hence it does not write to a stream directly, which can be + bad if files are large, say 1GB :). + Config ------ * Expand .get* methods of GitConfigParser to support default value. If it is not None, |