I'm not sure the author is aware of this story, but he cites the possible confusion with "Dolt" as the reason for naming his project "doit" in lowercase:
I've looked at a couple of data build tools and many will do basic jobs very well, and some of them will use even a nice dsl. Where I see many tools struggle is with task parameterization, which I found to be a frequent requirement for these kind of systems.
I have used PyDoit for various automation tasks and found it pretty useful. The author is very responsive as well and fixes problems in a timely manner. It's a good alternatice to Makefiles and libraries like fabric. Parametrization is an issue of course, but tasks can be easily customized using generators, which adds a lot of flexibility.
I was looking for a build-tool like system to "compile" my thesis: run data analysis scripts, output figures, do some munging on latex source and bibtex references, and finally run the latex compile.
After trying a few and fighting with waf when I needed more flexibility, I found doit to really be a godsend. It really seems to be the best mix of simplicity, flexibility, available features and extendability. Thought some of you might also find it useful. Plus, no arcane make syntax to learn or remember.
10 comments
[ 4.4 ms ] story [ 33.5 ms ] thread( http://www.folklore.org/StoryView.py?story=Do_It.txt )
http://pydoit.org/faq.html#why-is-doit-written-in-all-lowerc...
After trying a few and fighting with waf when I needed more flexibility, I found doit to really be a godsend. It really seems to be the best mix of simplicity, flexibility, available features and extendability. Thought some of you might also find it useful. Plus, no arcane make syntax to learn or remember.
I focused more on "saving keystrokes", though. Hence the autocomplete and the use of a one letter execute command.