ok
Direktori : /proc/thread-self/root/opt/alt/python36/lib64/python3.6/idlelib/__pycache__/ |
Current File : //proc/thread-self/root/opt/alt/python36/lib64/python3.6/idlelib/__pycache__/config.cpython-36.pyc |
3 � fޗ � @ s� d Z ddlmZ ddlZddlZddlmZ ddlZG dd� de�Z G dd� de�Z G d d � d e�ZG dd� de�ZG d d� de�Z G dd� de �ZG dd� d�Ze� Ze� Zdd� ZG dd� de�Zdd� Zedkr�ddlmZ edddd� dS )aE idlelib.config -- Manage IDLE configuration information. The comments at the beginning of config-main.def describe the configuration files and the design implemented to update user configuration information. In particular, user configuration choices which duplicate the defaults will be removed from the user's configuration files, and if a user file becomes empty, it will be deleted. The configuration database maps options to values. Conceptually, the database keys are tuples (config-type, section, item). As implemented, there are separate dicts for default and user values. Each has config-type keys 'main', 'extensions', 'highlight', and 'keys'. The value for each key is a ConfigParser instance that maps section and item to values. For 'main' and 'extenstons', user values override default values. For 'highlight' and 'keys', user sections augment the default sections (and must, therefore, have distinct names). Throughout this module there is an emphasis on returning useable defaults when a problem occurs in returning a requested configuration value back to idle. This is to allow IDLE to continue to function in spite of errors in the retrieval of config information. When a default is returned instead of a requested config value, a message is printed to stderr to aid in configuration problem notification and resolution. � )�ConfigParserN)�Fontc @ s e Zd ZdS )�InvalidConfigTypeN)�__name__� __module__�__qualname__� r r �3/opt/alt/python36/lib64/python3.6/idlelib/config.pyr # s r c @ s e Zd ZdS )�InvalidConfigSetN)r r r r r r r r $ s r c @ s e Zd ZdS )�InvalidFgBgN)r r r r r r r r % s r c @ s e Zd ZdS )�InvalidThemeN)r r r r r r r r &