delta/python-packages/gitpython.git/lib/git/async/pool.py, branch 3.1.2github.com: gitpython-developers/GitPython.git
Removed async from tree2010-06-12T12:34:09+00:00Sebastian Thielbyronimo@gmail.com2010-06-12T12:34:09+00:0086ea63504f3e8a74cfb1d533be9d9602d2d17e27
Cleaned up channel design, Reader and Writer bases don't require a channel anymore, but are abstract.2010-06-12T09:19:29+00:00Sebastian Thielbyronimo@gmail.com2010-06-12T09:19:18+00:00be8955a0fbb77d673587974b763f17c214904b57
Added IteratorReader, implementing the reader interface from an iterator. The implementation moved from the TaskIterator to the channel
Added IteratorReader, implementing the reader interface from an iterator. The implementation moved from the TaskIterator to the channel
test_task: fixed import error, made all modules from x import * safe2010-06-11T14:58:44+00:00Sebastian Thielbyronimo@gmail.com2010-06-11T14:58:44+00:00cac6e06cc9ef2903a15e594186445f3baa989a1a
Removed commented-out debug code and additional debug printings. Verified it works on py2.4, 2.5 and 2.62010-06-11T14:42:09+00:00Sebastian Thielbyronimo@gmail.com2010-06-11T14:42:09+00:00e14e3f143e7260de9581aee27e5a9b2645db72de
IMPORTANT: sometimes, when notifying waiters by releasing their lock, the 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 this2010-06-11T09:52:01+00:00Sebastian Thielbyronimo@gmail.com2010-06-11T09:52:01+00:006d1212e8c412b0b4802bc1080d38d54907db879d
Added dependency-task tests, and fixed plenty of ref-count related bugs, as 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 there2010-06-10T21:55:50+00:00Sebastian Thielbyronimo@gmail.com2010-06-10T21:55:50+00:00fbe062bf6dacd3ad63dd827d898337fa542931ac
Now tracking the amount of concurrent writers to assure the channel is 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 ...2010-06-10T13:38:40+00:00Sebastian Thielbyronimo@gmail.com2010-06-10T13:38:40+00:007c36f3648e39ace752c67c71867693ce1eee52a3
channel: Changed design to be more logical - a channel now has any amount of readers and writers, a ready is not connected to its writer anymore. This changes the refcounting of course, which is why the auto-cleanup for the pool is currently broken.2010-06-10T12:39:57+00:00Sebastian Thielbyronimo@gmail.com2010-06-10T12:39:57+00:0055e757928e493ce93056822d510482e4ffcaac2d
The benefit of this are faster writes to the channel, reading didn't improve, refcounts should be clearer now
The benefit of this are faster writes to the channel, reading didn't improve, refcounts should be clearer now
InputChannelTask now has interface for properly handling the reading from the same and different pools2010-06-10T08:14:32+00:00Sebastian Thielbyronimo@gmail.com2010-06-10T08:14:32+00:00cfb278d74ad01f3f1edf5e0ad113974a9555038d
messy first version of a properly working depth-first graph method, which allows the pool to work as expected. Many more tests need to be added, and there still is a problem with shutdown as sometimes it won't kill all threads, mainly because the process came up with worker threads started, which cannot be2010-06-09T22:24:49+00:00Sebastian Thielbyronimo@gmail.com2010-06-09T22:24:49+00:003323464f85b986cba23176271da92a478b33ab9c