coh2

not entirely but to a degree yes as that will allow anyone to add a custom storage backend with ease.

that's where the `abc` kicks in, as with it, we can define a set of functionality we need and leave it to the backend to do whatever it takes in...

head up: done with the table layout (except for testing when the backend is done), half of the backend implementation remains. Will likely be another week(end) until it is fully...

problem with those deps is that they're development pieces of the respective libs and almost every distro uses a different naming scheme and/or versions. Given that lxml also needs gcc...

judging by a quick search, it seems to be an upstream regression [1,2,3] or a timeout/connectivity issue[4] will add a try/except and work around it. [1] http://code.google.com/p/httplib2/issues/detail?id=96 [2] https://code.google.com/p/httplib2/issues/detail?id=101 [3]...

also, I wonder if making the sleep time a bit random would help as the remote might wrongly assumes that a DoS is going on and tries to block some...

Perhaps another two solutions: - listen on stdin for new keywords - add-in zeromq and use that for multi-way IPC (unix socket, tcp/ip ...) As for the observer option: inotify...

Pretty much so but prior to doing that, I'd like to create some sort of config parsing so that a user won't have to edit `gather.py` by hand. Then, finish...

a quick heads up. I'm working on finishing the config file format(s). So far I've got a usable raw python config format but I'm also working on something ini-base (stdlib...

> It's reached a point where I am reluctant to commit That's what branches and issue trackers are for; that way, one can keep in touch/sync > This is so...