summaryrefslogtreecommitdiff
path: root/lib/git
Commit message (Collapse)AuthorAgeFilesLines
* win32 compatability adjustmentsunknown2010-07-024-8/+13
|
* Fixed broken 0.2 documentation, it didn't contain the API reference ↵Sebastian Thiel2010-07-021-0/+0
| | | | previously due to import errors and a somewhat inconsistent working tree that occurred when switching branches ...
* Added further information about the required submodules, and how to install ↵Sebastian Thiel2010-07-011-0/+0
| | | | them. Incremeneted version to 0.3.0 beta1
* Removed blob.data property as there is no real reason for an exception to ↵Sebastian Thiel2010-06-291-11/+1
| | | | the rule of trying not to cache possibly heavy data. The data_stream method should be used instead
* Renamed modules utils to util, and errors to exc to be more conforming to ↵Sebastian Thiel2010-06-2917-26/+26
| | | | the submodules's naming conventions
* Removed repo tests which for some reason left the 'repos' directory around, ↵Sebastian Thiel2010-06-291-1/+6
| | | | replaced them by a real test which actually executes code, and puts everything into the tmp directory
* Updated and fixed sphinx API docs, which included one quick skim-throughSebastian Thiel2010-06-2911-52/+82
|
* Diff: fixed bug that caused a string to end up as a blob modeSebastian Thiel2010-06-297-13/+16
|
* All tests adjusted to work with the changed internal sha representationSebastian Thiel2010-06-289-39/+54
|
* Adjusted all files to (hopefully) deal with the fact that all objects now ↵Sebastian Thiel2010-06-2520-3278/+2740
| | | | | | | use 20 byte sha's internally as it is closer to the GitDB implementation Switched all remaining files back to tabs Adjusted all remaining docstrings to suit the sphinx doc convention - its likely that there are many of docstring syntax errors though
* index.reset is now partly implemented using python, but in fact it resorts ↵Sebastian Thiel2010-06-252-20/+34
| | | | to using git-read-tree to keep the stat information when merging one tree in. After all this is what needed to be implemented in python as well
* IndexFile.add: writing of the index file can now optionally be turned off. ↵Sebastian Thiel2010-06-241-6/+12
| | | | The default is to write the physical index, which is the behaviour you would expect
* GitCmdStreamReader: fixed terrible bug which only kicked in if the stream ↵Sebastian Thiel2010-06-243-6/+19
| | | | | | was actually empty. This is a rare case that can happen during stream testing. Theoretically there shouldn't be any empty streams of course, but practically they do exist sometimes ;); fixed stream.seek implementation, which previously used seek on standard output Improved GitCmd error handling
* aggressive_tree_merge: fixed incorrect handling of one branch, it was just ↵Sebastian Thiel2010-06-244-5/+12
| | | | | | not implemented causing incorrect merge results. Added test to cover this issue Diff: added NULL_BIN_SHA constant for completeness
* Multiple partly critical bugfixes related to index handlingSebastian Thiel2010-06-243-9/+33
|
* fixed critical bug in traverse_trees_recursive, implemented IndexFile.new ↵Sebastian Thiel2010-06-233-11/+19
| | | | including simple test, it may be simple as the methods it uses are throroughly tested
* Added test for aggressive_tree_mergeSebastian Thiel2010-06-233-65/+69
|
* Implemented simple tree merging and a simple test, more elaborate testing is ↵Sebastian Thiel2010-06-231-8/+78
| | | | in progress
* Initial frame for implementing read_tree using pure python. As git-read-tree ↵Sebastian Thiel2010-06-224-8/+165
| | | | | | | can do much more than we can ( and faster assumably ), the .new method is used to create new index instances from up to 3 trees. Implemented multi-tree traversal to facilitate building a stage list more efficiently ( although I am not sure whether it could be faster to use a dictionary together with some intensive lookup ), including test Added performance to learn how fast certain operations are, and whether one should be preferred over another
* index.write_tree: now uses MemoryDB, making tree handling more efficient as ↵Sebastian Thiel2010-06-222-3/+7
| | | | IO will only be done when required. A possible disadvantage though is that time is spent on compressing the trees, although only the raw data and their shas would theoretically be needed. On the other hand, compressing their data uses less memory. An optimal implementation would just sha the data, check for existance, and compress it to write it to the database right away. This would mean more specialized code though, introducing redundancy. If IStreams would know whether they contain compressed or uncompressed data, and if there was a method to get a sha from data, this would work nicely in the existing framework though
* Tree-Writing now works after fixing an off-by-one errorSebastian Thiel2010-06-222-12/+13
|
* index.write_tree: initial version implemented, although its not yet working ↵Sebastian Thiel2010-06-2211-187/+266
| | | | | | | correctly, a test to explicitly compare the git version with the python implementation is still missing Tree and Index internally use 20 byte shas, converting them only as needed to reduce memory footprint and processing time objects: started own 'fun' module containing the most important tree functions, more are likely to be added soon
* index: put serialization methods into new 'fun' module, this makes the calls ↵Sebastian Thiel2010-06-212-137/+183
| | | | faster as it removes one level of indirection, and makes the main file smaller, improving maintainability
* index.add does not need the git clt anymoreSebastian Thiel2010-06-212-24/+9
|
* index: Entries are now using flags internally, instead of reducing the flag ↵Sebastian Thiel2010-06-214-60/+83
| | | | information to just the stage ( just to be closer to the git-original )
* index.add: now uses gitdb.store functionality instead of git-hash-file. The ↵Sebastian Thiel2010-06-212-53/+57
| | | | python version is about as fast, but could support multithreading using async
* db: added pure python git databaseSebastian Thiel2010-06-203-771/+775
| | | | repo: now has the option to use the pure python git database implementation, which is currently not used though
* GitCmd implementation of gitdb base moved to git-python where it belongs. ↵Sebastian Thiel2010-06-184-4/+51
| | | | Previously it was located in gitdb, which doesn't have any facilities to use the git command
* Move LazyMixin type to gitdb, index reading now uses file_contents_ro from ↵Sebastian Thiel2010-06-153-39/+7
| | | | gitdb as well
* Moved LockedFD and its test into the gitdb projectSebastian Thiel2010-06-152-141/+3
|
* Reimplemented Lock handling to be conforming to the git lock protocol, which ↵Sebastian Thiel2010-06-153-78/+133
| | | | | | is actually more efficient than the previous implementation Index now locks its file for reading, and properly uses LockedFD when writing
* Moved small types that had their own module into the utils moduleSebastian Thiel2010-06-148-488/+482
|
* Implemented the serializable interface - by refactoring codeSebastian Thiel2010-06-141-32/+47
|
* index: split index file into multiple files of a single package. This didn't ↵Sebastian Thiel2010-06-146-1438/+1439
| | | | reduce the file size as much as I would have liked, but certainly is a start for further 'outsourcing'
* tree: added TreeModifier, allowing to adjust existing trees safely and or ↵Sebastian Thiel2010-06-144-11/+94
| | | | fast, while staying compatible with serialization which requires it to be sorted
* tree now uses less memory for its cache as it stores the bare deserialized ↵Sebastian Thiel2010-06-141-55/+63
| | | | information - this also speeds up later serialization after changes. its clear though that retrieving actual objects is slower currently as these are not cached anymore. Its worth thinking about moving these encoding, decoding routines to gitdb
* Implemented initial version of tree serialization which appears to work ↵Sebastian Thiel2010-06-143-235/+281
| | | | | | | according to a simple test ( presort still needs implementation ) submodule: added stub to allow the tree to return something, its not implemented though
* Removed odb from project, it is now used as a submodule named gitdb, which ↵Sebastian Thiel2010-06-1211-993/+24
| | | | | | was added instead Adjusted all imports to deal with the changed package names
* Removed async from treeSebastian Thiel2010-06-127-1688/+0
|
* task: improved naming of task types, improved pool test to be less dependent ↵Sebastian Thiel2010-06-121-10/+16
| | | | on starting with just the main thread
* channel: cleaned up inheritance hierarchy, adding mixing for callback ↵Sebastian Thiel2010-06-121-10/+23
| | | | functionality - previously the callback functionality was bound to channel based readers/writers
* Cleaned up channel design, Reader and Writer bases don't require a channel ↵Sebastian Thiel2010-06-123-75/+130
| | | | | | anymore, but are abstract. Added IteratorReader, implementing the reader interface from an iterator. The implementation moved from the TaskIterator to the channel
* Added performance test, improved iterator task which will now be usable by ↵Sebastian Thiel2010-06-111-0/+3
| | | | default. It shows that there must be the notion of a producer, which can work if there are no items read
* test_task: fixed import error, made all modules from x import * safeSebastian Thiel2010-06-115-1/+15
|
* Removed commented-out debug code and additional debug printings. Verified it ↵Sebastian Thiel2010-06-113-13/+0
| | | | works on py2.4, 2.5 and 2.6
* Improved shutdown handling - although its impossible to prevent some stderr ↵Sebastian Thiel2010-06-112-8/+46
| | | | printing thanks to the underlying threading implementation, we can at least make sure that the interpreter doesn't block during shutdown. Now it appears to be running smoothly
* IMPORTANT: sometimes, when notifying waiters by releasing their lock, the ↵Sebastian Thiel2010-06-113-6/+5
| | | | lock is not actually released or they are not actually notifyied, staying in a beautysleep. This glitch is probably caused by some detail not treated correctly in the thread python module, which is something we cannot fix. It works most of the time as expected though - maybe some cleanup is not done correctly which causes this
* Added dependency-task tests, and fixed plenty of ref-count related bugs, as ↵Sebastian Thiel2010-06-104-25/+44
| | | | well as concurrency issues. Now it works okay, but the thread-shutdown is still an issue, as it causes incorrect behaviour making the tests fail. Its good, as it hints at additional issues that need to be solved. There is just a little more left on the feature side, but its nearly there
* tasks can now terminate faster when no items were read, without neglecting ↵Sebastian Thiel2010-06-101-19/+24
| | | | their duty to close the channel if required. Code is a little less maintainable now, but faster, it appears
* Now tracking the amount of concurrent writers to assure the channel is ↵Sebastian Thiel2010-06-102-29/+59
| | | | closed only when there is no one else writing to it. This assures that all tasks can continue working, and put their results accordingly. Shutdown is still not working correctly, but that should be solvable as well. Its still not perfect though ...