Whoops, missed the other question: I didn’t know about *that* apachelog project at the time loghetti was developed. In the meantime, I found one that was written pretty simply and sanely, and we were able to get it to do what we wanted pretty easily. It probably wouldn’t be too difficult to replace what we have, but it’s just not clear to me that the project you point to adds a lot of value for the added overhead. That project is also written pretty simply (and sanely), but I’m not a fan of how it puts together the dictionary, and the module that ships with loghetti is a generator model, which I also like for dealing with very large log files (several million lines) without taxing resources too much, etc. I’m willing to be sold, though, if you wish to do a comparison of how the two work and report back any benefits you perceive in using the newer module.

I also would rather not be tracking changes of yet another project to insure that loghetti is always in a working state.

I should probably do a good code review and/or at the very least write tests for the thing before I do that, though. I don’t really want to have a breakneck release cycle that involves deployment to the cheeseshop and end users being constantly 3 versions behind.

Thanks for the suggestion, though — I’ll make it a goal to get things in shape for that to happen (you could submit an issue on github as an added reminder, too).

Just curious: did you consider using [apachelog](http://pypi.python.org/pypi/apachelog)?

Also, I’m unable to find Loghetti at the Cheeseshop. Any plans to upload there?

Thanks.