as a centralized repository of settings. You normally import the singleton and access its (many) attributes directly: from conda.base.context import context context.quiet # False This singleton is initialized higher precedence: 1. Default values hardcoded in the Context class. These are defined via class attributes. 2. Values defined in the configuration files (.condarc), which have their own precedence. 3 Developer guide conda, Release 23.7.4.dev7 When MyConfiguration is instantiated, those class attributes are populated by the .raw_data dicionary that has been filled in with the values coming from the

as a centralized repository of settings. You normally import the singleton and access its (many) attributes directly: from conda.base.context import context context.quiet # False This singleton is initialized higher precedence: 1. Default values hardcoded in the Context class. These are defined via class attributes. 2. Values defined in the configuration files (.condarc), which have their own precedence. 3 Developer guide conda, Release 23.9.1.dev1 When MyConfiguration is instantiated, those class attributes are populated by the .raw_data dicionary that has been filled in with the values coming from the

as a centralized repository of settings. You normally import the singleton and access its (many) attributes directly: from conda.base.context import context context.quiet # False This singleton is initialized higher precedence: 1. Default values hardcoded in the Context class. These are defined via class attributes. 2. Values defined in the configuration files (.condarc), which have their own precedence. 3 Developer guide 335 conda, Release 23.10.1.dev3 When MyConfiguration is instantiated, those class attributes are populated by the .raw_data dicionary that has been filled in with the values coming from the

as a centralized repository of settings. You normally import the singleton and access its (many) attributes directly: from conda.base.context import context context.quiet # False This singleton is initialized higher precedence: 1. Default values hardcoded in the Context class. These are defined via class attributes. 2. Values defined in the configuration files (.condarc), which have their own precedence. 3 Developer guide 337 conda, Release 23.11.1.dev1 When MyConfiguration is instantiated, those class attributes are populated by the .raw_data dicionary that has been filled in with the values coming from the

as a centralized repository of settings. You normally import the singleton and access its (many) attributes directly: from conda.base.context import context context.quiet # False This singleton is initialized higher precedence: 1. Default values hardcoded in the Context class. These are defined via class attributes. 2. Values defined in the configuration files (.condarc), which have their own precedence. 3 Contributors welcome conda, Release 24.1.2.dev2 When MyConfiguration is instantiated, those class attributes are populated by the .raw_data dicionary that has been filled in with the values coming from the

as a centralized repository of settings. You normally import the singleton and access its (many) attributes directly: from conda.base.context import context context.quiet # False This singleton is initialized higher precedence: 1. Default values hardcoded in the Context class. These are defined via class attributes. 2. Values defined in the configuration files (.condarc), which have their own precedence. 3 Contributors welcome conda, Release 24.3.1.dev2 When MyConfiguration is instantiated, those class attributes are populated by the .raw_data dicionary that has been filled in with the values coming from the

as a centralized repository of settings. You normally import the singleton and access its (many) attributes directly: from conda.base.context import context context.quiet # False This singleton is initialized higher precedence: 1. Default values hardcoded in the Context class. These are defined via class attributes. 2. Values defined in the configuration files (.condarc), which have their own precedence. 3 Contributors welcome conda, Release 24.3.1.dev7 When MyConfiguration is instantiated, those class attributes are populated by the .raw_data dicionary that has been filled in with the values coming from the

as a centralized repository of settings. You normally import the singleton and access its (many) attributes directly: from conda.base.context import context context.quiet # False This singleton is initialized higher precedence: 1. Default values hardcoded in the Context class. These are defined via class attributes. 2. Values defined in the configuration files (.condarc), which have their own precedence. 3 Contributors welcome conda, Release 24.5.1.dev1 When MyConfiguration is instantiated, those class attributes are populated by the .raw_data dicionary that has been filled in with the values coming from the

as a centralized repository of settings. You normally import the singleton and access its (many) attributes directly: from conda.base.context import context context.quiet # False This singleton is initialized higher precedence: 1. Default values hardcoded in the Context class. These are defined via class attributes. 2. Values defined in the configuration files (.condarc), which have their own precedence. 3 ParameterLoader(MapParameter({"key": 1.0}, float)) When MyConfiguration is instantiated, those class attributes are populated by the .raw_data dicionary that has been filled in with the values coming from the

as a centralized repository of settings. You normally import the singleton and access its (many) attributes directly: from conda.base.context import context context.quiet # False This singleton is initialized higher precedence: 1. Default values hardcoded in the Context class. These are defined via class attributes. 2. Values defined in the configuration files (.condarc), which have their own precedence. 3 ParameterLoader(MapParameter({"key": 1.0}, float)) When MyConfiguration is instantiated, those class attributes are populated by the .raw_data dicionary that has been filled in with the values coming from the