For whatever reason I didn't use it in Paste Deploy, but INITools is a
separate config parser from ConfigParser, but compatible, and you can
enable some typical options fairly easily (things like ${} parsing,
similar to how buildout config files work):
http://pythonpaste.org/initools/On Mon, Oct 26, 2009 at 3:48 PM, Iain Duncan <[email protected]> wrote: > > Hi folks, wondering if anyone can tell what Pylons (Paste?) uses for > parsing the ini files. I'm breaking some of my app into it's own package > and want to have it parse a local ini file if that component gets used > on it's own separately from the pylons app, but I'd like to use whatever > is the standard in Pylons to do so. > > Thanks > Iain > > > > > -- Ian Bicking | http://blog.ianbicking.org | http://topplabs.org/civichacker --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
