On Tue, May 20, 2014 at 11:49 AM, Chris Angelico <ros...@gmail.com> wrote: > Okay, I won't suggest Windows INI files, but I'll still suggest taking > a step back and figuring out exactly what you're trying to accomplish. > Can you separate out the real data from the formula-derived info, put > the former into a git-managed file, and the latter into something you > regenerate by script (maybe off a makefile)?
Actually, I'm sympathetic to INI files. I like the simplicity. The ultimate config files are output in XML though (ugh). Somewhere along the way, I want to avoid typing repetitive information into files. Today, I use a template file, read the spreadsheet with xlrd and generate the XML cruft with Cheetah. I could retain Excel (or Open Document or pyspread or some other spreadsheet) and then export to CSV files. That would solve the issue as well. Though it would be an extra step I'd have to do manually (because I can rely on xlrd), it would still leave me with the input-to-config-file data in tabular form. I'll figure something out. Something else that occurs to me as I write this is that Excel files tend to acquire all sorts of cruft, right? Or is that just Word files? Perhaps I can make things better by copying/pasting the existing spreadsheet data into a fresh spreadsheet that hasn't been updated repeatedly? Skip -- https://mail.python.org/mailman/listinfo/python-list