|
From: Maurits v. R. <ma...@va...> - 2003-11-28 10:59:34
|
Reinout van Rees wrote: > The solution I'm thinking of is that of weex > (http://weex.sourceforge.net). It uses a config file with named > settings. If I do 'weex lexicon' it executes the commands in the > config file belonging to that label. 'weex ifes' happily uploads the > entire ifes website. > > This same idea can of course be implemented for stats too, but I > suggest starting with statsgen. 'statsgen.py delft'. 'statsgen.py > hannover1'. You get the idea. I have a shell script that does something similar: ./plan.sh haven [-other options] sees "haven" and then knows what the uploadscript is called and which player is playing and which master config to use, etc. We could make a statsgen.rc: game=haven player=9 master=~/pl/Mhaven game=emp player=8 master=~/pl/Memp > You *have* printed out the python coding rules (it's in a PEP > somewhere)? [For the unenlightened: Python Enhancement Proposal]. Hm: http://www.python.org/peps/ lists quite a lot of peps. I don't see anything that resembles any basic coding rules. Care to list your favorite peps? -- Maurits van Rees | ma...@va... http://maurits.vanrees.org/ "Peace is not the absence of war; it is the absence of fear." |