|
![]() |
|
Well it was a busy day for me in Python land:
Just have to add a good recipes mechanism and Vellum should be great. I’m leaning toward a template system that lets you put a recipe on one of your lines and the required options and that will generate new lines to be run. That or a simple way to just load other files and access that file’s tasks in a namespace. Or maybe both, gotta see what I need. I was also talking with some friends, and they mentioned it’d be great if Vellum could distribute the builds to multiple machines in such a way that nobody needs to actually enter IP addresses. I’ve always wanted this too, but never thought of doing a build tool. Now that I have a fairly complete one, I think I’ll just try making this feature. I don’t really need something like this yet, but I can see having to run tons of tests on the code in my book and all my projects. Being able to push that out to the many machines in my closet will be nice. What I’m thinking is using PyZeroConf or Avahi so that all the machines will announce themselves and their roles, and then a master pushes the Vellum script to them and runs targets using HTTP. So far I’m really enjoying making stuff with Python. Zapps is very useful for the little parsers I want. Idiopidae is great for writing the docs and working good for my book so far. Now “Vellum” will help build my book and all the required software in the way I’ve always wanted these things built. |