ó Xé?_c@sddZyddlmZWn!ek r=ddlmZnXyeWn!ek riddlmZnXyeWnek r‹e ZnXyddl Z Wnek r»ddl Z nXddl Z ddlZd„Zdefd„ƒYZdefd „ƒYZd efd „ƒYZd dd „ƒYZddd„ƒYZd„Zd„Zd„ZdS(såGeneric configuration system using unrepr. Configuration data may be supplied as a Python dictionary, as a filename, or as an open file object. When you supply a filename or file, Python's builtin ConfigParser is used (with some extensions). Namespaces ---------- Configuration keys are separated into namespaces by the first "." in the key. The only key that cannot exist in a namespace is the "environment" entry. This special entry 'imports' other config entries from a template stored in the Config.environments dict. You can define your own namespaces to be called when new config is merged by adding a named handler to Config.namespaces. The name can be any string, and the handler must be either a callable or a context manager. iÿÿÿÿ(t ConfigParser(tSetNcCsLt|tƒr$tƒj|ƒ}n$t|dƒrHtƒj|ƒ}n|S(sDReturn a dict from 'config' whether it is a dict, file, or filename.tread(t isinstancet basestringtParsertdict_from_filethasattr(tconfig((s|/local/mnt/workspace/CRMBuilds/Saipan.LA.2.0-00145-STD.PROD-1_20200821_083004/b/common/sectools/ext/cherrypy/lib/reprconf.pytas_dict0s t NamespaceSetcBs/eZdZd„Zd„Zd„ZeZRS(sEA dict of config namespace names and handlers. Each config entry should begin with a namespace name; the corresponding namespace handler will be called once for each config entry in that namespace, and will be passed two arguments: the config key (with the namespace removed) and the config value. Namespace handlers may be any Python callable; they may also be Python 2.5-style 'context managers', in which case their __enter__ method should return a callable to be used as the handler. See cherrypy.tools (the Toolbox class) for an example. c Cs}i}xU|D]M}d|kr |jddƒ\}}|j|iƒ}||||s6        L46rs