Size: 5938
Comment:
|
Size: 6689
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 140: | Line 140: |
Note: You should specify the coding used in the .py file. In this case is utf-8. Then I assign x.common.name with a unicode string. | Note: You should specify the coding used in the .py file. In this case is utf-8. Then I assign x.common.name with a unicode string. If you don't specify the encoding in create instance of the DictIni, the Dict4Ini will auto find the default encoding in the system in turns of: * local.getdefaultlocale()[1] * sys.getfilesystemencoding() * utf-8 |
Line 162: | Line 166: |
==== Example 6 Using multi section ==== {{{#!python import dict4ini x = dict4ini.DictIni('test.ini') x.common.settings.a = 1 x.common.settings.b = ["3", "hello"] x.special.name = 'limodou' x.special.homepage = 'http://www.donews.net/limodou' x.save()}}} You don't need to care if subsection is created, you need to just use it. The result of the ini file will be: {{{ [common/settings] a = 1 b = "3",hello, [special] homepage = http://www.donews.net/limodou name = limodou}}} |
::-- limodou [DateTime(2005-09-14T06:31:19Z)] TableOfContents
1. Dict4Ini
This module is used to process ini format configuration file. It acts just like a dict, but you can also access it's sections and options with attribute syntax, just like x.test.
1.1. Why reinvent this module?
I used Config4Obj module for GoogleTalkBot software (confbot) to deal with configuration file. But I found its lacks on:
- Only can access options as x['name']['o'], but not as x.name.o
- You must create section first, then you can access its options. So if you didn't create x['name']={} section, so you cann't do x['name']['o'] = 3
The option's data can be saved as string format, but as read out again, Config4Obj cann't convert it to their original value type, so you must conver it yourself. I didn't tried validate module ships with Config4Obj.
- Didn't support unicode
Above is only my opinions, so they may be not right.
So I decide to reinvent a new module to solve these lacks, I named it as Dict4Ini, it means you can access the config object just like a dict.
1.2. What's it features
- as simple as others
- you can access options according to dict syntax, just like x['name']['o'] = 1, x['name'].keys(), x['name'].values(), etc.
- you also can access options according to attr syntax, just like x.name.o = 1, x.name.keys(), x.name.values(), etc. So the name must be Identifier or single word.
- you can save comments in it(but this feature is not tested so much)
- support multi level section, subsection name will just like: [firsub/secsub]
- It's a little module, just for my mind, so if you like, you could try it, but if you don't like, just skip it, that's ok
1.3. Where can I download it?
Visit the http://wiki.woodpecker.org.cn/moin/Dict4Ini site
- Download it from here attachment:dict4ini.py
1.4. Examples
1.4.1. Example 1 Create a ini file
This example will save option to test.ini. As you can see, you needn't create section "common" at first, just think it's there, it's ok. The result of test.ini is:
{{{[common] list = 3,Hello,"have spaces", bool = 1 name = limodou}}}
And you can see, once the value has special chars, just like ' ', ',', '\"', etc, the string will be quoted by double quoter. But "Hello" is a single word, and it has not the special chars, so it won't be quoted. If the value is number, it'll be just like number literal, but if the value is number string, it'll be quoted by double quoter.
In this time, the Dict4Ini support number, list, string, unicode data type, for others you should convert yourself.
1.4.2. Example 2 Open an existed ini file
So it's easy. The result will be: