In reviewing pyant, I'm really impressed with how advanced the system is for being programmed in 2002, as well as how the system works with a much more recent version of python, and on a Mac, whereas the majority of pyant was developed on windows.
While breaking pyant to figure out how it works by changing its name to fwcuug, I realize how important name spaces are in python. Its pretty cool how much structure you can add to python functions, modules, and packages through the simple use of namespaces.
My to-do list for fwcuug is to start writing some basic buildfiles to get more acquainted with its current state, i.e. which tasks are fully baked and which ones need more time. I think the code itself does need some cleanup, as there are a lot of "from module import *" which if I recall correctly, I read in "Learning Python" can be a bad practice. I'm interested to learn more about the XML and XSL capabilities of python by working on fwcuug, which will likely help my work with Nexista, Schematronic, and pycoon. Eventually I'd like to try packaging fwcuug as a python egg and submit it to the cheese shop.
While breaking pyant to figure out how it works by changing its name to fwcuug, I realize how important name spaces are in python. Its pretty cool how much structure you can add to python functions, modules, and packages through the simple use of namespaces.
My to-do list for fwcuug is to start writing some basic buildfiles to get more acquainted with its current state, i.e. which tasks are fully baked and which ones need more time. I think the code itself does need some cleanup, as there are a lot of "from module import *" which if I recall correctly, I read in "Learning Python" can be a bad practice. I'm interested to learn more about the XML and XSL capabilities of python by working on fwcuug, which will likely help my work with Nexista, Schematronic, and pycoon. Eventually I'd like to try packaging fwcuug as a python egg and submit it to the cheese shop.
Like Ant and phing, a reincarnation of pyant from 2002.
