automatic import of python-config2

3 files changed, 891 insertions, 0 deletions

diff --git a/.gitignore b/.gitignore
index e69de29..7134df0 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/config2-0.3.2.tar.gz
diff --git a/python-config2.spec b/python-config2.spec
new file mode 100644
index 0000000..4ae2862
--- /dev/null
+++ b/python-config2.spec
@@ -0,0 +1,889 @@
+%global _empty_manifest_terminate_build 0
+Name:		python-config2
+Version:	0.3.2
+Release:	1
+Summary:	Python application configuration - highly inspired by `node-config`.
+License:	MIT
+URL:		https://github.com/grimen/python-config2
+Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/df/ee/c0548078db70217616ac355b938a1be0a9d8c5427844ad719eb407229237/config2-0.3.2.tar.gz
+BuildArch:	noarch
+
+Requires:	python3-colour-runner
+Requires:	python3-setupextras
+Requires:	python3-rootpath
+Requires:	python3-attributedict
+Requires:	python3-inspecta
+Requires:	python3-mybad
+Requires:	python3-deepmerge
+Requires:	python3-pyyaml
+Requires:	python3-six
+Requires:	python3-deepdiff
+Requires:	python3-tox
+Requires:	python3-coverage
+Requires:	python3-codecov
+
+%description
+
+# `config2` [![PyPI version](https://badge.fury.io/py/config2.svg)](https://badge.fury.io/py/config2) [![Build Status](https://travis-ci.com/grimen/python-config2.svg?branch=master)](https://travis-ci.com/grimen/python-config2) [![Coverage Status](https://codecov.io/gh/grimen/python-config2/branch/master/graph/badge.svg)](https://codecov.io/gh/grimen/python-config2)
+
+*Python environment configuration simplified.*
+
+
+## Introduction
+
+**Config2** (for Python) - which is highly inspired by [`node-config`](https://github.com/lorenwest/node-config) - organizes hierarchical configurations for your app deployments.
+
+It lets you define a set of default parameters, and extend them for different deployment environments (development, qa, staging, production, etc.).
+
+Configurations are stored in **configuration files** within your application, and can be overridden and extended by **environment variables**, **command line parameters**, or **external sources**.
+
+This gives your application a consistent configuration interface shared among a growing list of npm modules also using node-config.
+
+**NOTE:** This project is more or less in pair with [`node-config`](https://github.com/lorenwest/node-config) implementation, with exception for some fluff that could be considered too much magic such as deployment specific *multi-instance deployments* which I so far haven't found any good motivation for, and some other questionable advanced features mentioned in the wiki pages.
+
+
+## Project Guidelines
+
+...based on [`node-config`](https://github.com/lorenwest/node-config) project guidelines:
+
+- *Simple* - Get started fast
+- ~~*Powerful* - For multi-node enterprise deployment~~ - excluded because [with power comes responsability](https://en.wikipedia.org/wiki/Principle_of_least_astonishment)
+- *Flexible* - Supporting multiple config file formats
+- *Lightweight* - Small file and memory footprint
+- *Predictable* - Well tested foundation for module and app developers
+
+
+## Install
+
+Install using **pip**:
+
+```sh
+$ pip install config2
+```
+
+
+## Use
+
+**1.** Assuming we have a **python application** project...
+
+```
+some_project
+└── app.py
+```
+
+`app.py` - some app making serious **$$$**
+
+```python
+# business logic
+print('$$$')
+```
+
+
+**2.** Let's add some environment specific **config files**...
+
+```
+some_project
+└── config
+    ├── default.yml
+    ├── development.yml
+    ├── foo.yml
+    └── production.yml
+└── app.py
+```
+
+`default.yml` - with some bogus nested settings shared for all environments (defaults)
+
+```yaml
+a1: DEFAULT 1
+a2:
+    b1: [1, 2, 3]
+    b2:
+        -   foo
+        -   bar
+    b3:
+        c1: 1
+        c2: "DEFAULT 2"
+```
+
+`development.yml` - with some bogus nested settings overriden for `development` environment (overriden)
+
+```yaml
+a2:
+    b2:
+        -   DEV 1
+    b3:
+        c2: "DEV 2"
+some_key_only_for_dev: true
+```
+
+`foo.yml` - with some bogus nested settings overriden for `foo` environment (overriden)
+
+```yaml
+a2:
+    b2:
+        -   FOO 1
+    b3:
+        c2: "FOO 2"
+some_key_only_for_foo: true
+```
+
+`production.yml` - with some bogus nested settings overriden for `production` environment (overriden)
+
+```yaml
+a2:
+    b2:
+        -   PROD 1
+    b3:
+        c2: "PROD 2"
+some_key_only_for_prod: true
+```
+
+
+**3.** Let's now **run the app** using **various environments**...
+
+`$ python app.py`
+
+```python
+from config2.config import config
+
+config.get_env() # => None
+config.get() # => {'a1': 'DEFAULT 1', 'a2': {'b1': [1, 2, 3], 'b2': ['foo', 'bar'], 'b3': {'c1': 1, 'c2': 'DEFAULT 2'}}}
+
+config.a1 # => 'DEFAULT 1'
+config.a2 # => {'b1': [1, 2, 3], 'b2': ['foo', 'bar'], 'b3': {'c1': 1, 'c2': 'DEFAULT 2'}}
+config.a2.b3.c2 # => 'DEFAULT 2'
+
+print('$$$')
+```
+
+`$ ENV=development python app.py`
+
+```python
+from config2.config import config
+
+config.get_env() # => 'development'
+config.get() # => {'a1': 'DEFAULT 1', 'a2': {'b1': [1, 2, 3], 'b2': ['DEV 1'], 'b3': {'c1': 1, 'c2': 'DEV 2'}}, 'some_key_only_for_dev': True}
+
+config.a1 # => 'DEFAULT 1'
+config.a2 # => {'b1': [1, 2, 3], 'b2': ['DEV 1'], 'b3': {'c1': 1, 'c2': 'DEV 2'}}
+config.a2.b3.c2 # => 'DEV was here 2'
+
+config.some_key_only_for_dev # => True
+
+config.some_key_only_for_foo # => AttributeError
+config.some_key_only_for_prod # => AttributeError
+
+print('$$$')
+```
+
+`$ ENV=foo python app.py`
+
+```python
+from config2.config import config
+
+config.get_env() # => 'foo'
+config.get() # => {'a1': 'DEFAULT 1', 'a2': {'b1': [1, 2, 3], 'b2': ['FOO 1'], 'b3': {'c1': 1, 'c2': 'FOO 2'}}, 'some_key_only_for_foo': True}
+
+config.a1 # => 'DEFAULT 1'
+config.a2 # => {'b1': [1, 2, 3], 'b2': ['FOO 1'], 'b3': {'c1': 1, 'c2': 'FOO 2'}}
+config.a2.b3.c2 # => 'FOO was here 2'
+
+config.key_only_for_foo # => True
+
+config.some_key_only_for_dev # => AttributeError
+config.some_key_only_for_prod # => AttributeError
+
+print('$$$')
+```
+
+`$ ENV=production python app.py`
+
+```python
+from config2.config import config
+
+config.get_env() # => 'production'
+config.get() # => {'a1': 'DEFAULT 1', 'a2': {'b1': [1, 2, 3], 'b2': ['PROD 1'], 'b3': {'c1': 1, 'c2': 'PROD 2'}}, 'some_key_only_for_foo': True}
+
+config.a1 # => 'DEFAULT 1'
+config.a2 # => {'b1': [1, 2, 3], 'b2': ['PROD 1'], 'b3': {'c1': 1, 'c2': 'PROD 2'}}
+config.a2.b3.c2 # => 'PROD was here 2'
+
+config.some_key_only_for_prod # => True
+
+config.some_key_only_for_dev # => AttributeError
+config.some_key_only_for_foo # => AttributeError
+
+print('$$$')
+```
+
+etc.
+
+
+**4.** Optionally, let's now introduce custom **config environment variables**...
+
+
+```
+some_project
+└── config
+    ├── custom-environment-variables.yml
+    ├── default.yml
+    ├── development.yml
+    ├── foo.yml
+    └── production.yml
+└── app.py
+```
+
+`custom-environment-variables.yml` - with mappings of config keys to environment variables
+
+```yaml
+a1: A1
+a2:
+    b3:
+        c2: C2
+```
+
+**5.** Let's now **run the app** using **custom environment variables** to override config...
+
+`$ A1=x C2=y python app.py`
+
+```python
+from config2.config import config
+
+config.get_env() # => None
+config.get() # => {'a1': 'x', 'a2': {'b1': [1, 2, 3], 'b2': ['foo', 'bar'], 'b3': {'c1': 1, 'c2': 'y'}}}
+
+config.a1 # => 'x'
+config.a2 # => {'b1': [1, 2, 3], 'b2': ['foo', 'bar'], 'b3': {'c1': 1, 'c2': 'y'}}
+config.a2.b3.c2 # => 'y'
+
+print('$$$')
+```
+
+
+## Test
+
+Clone down source code:
+
+```sh
+$ make install
+```
+
+Run **colorful tests**, with only native environment (dependency sandboxing up to you):
+
+```sh
+$ make test
+```
+
+Run **less colorful tests**, with **multi-environment** (using **tox**):
+
+```sh
+$ make test-tox
+```
+
+
+## About
+
+This project was mainly initiated - in lack of existing alternatives - to be used at our work at **[Markable.ai](https://markable.ai)** to have common code conventions between various programming environments where **Python** (research, CV, AI) and **Node.js** (I/O, APIs, UIs, scripts) currently are most used.
+
+
+## License
+
+Released under the MIT license.
+
+
+
+
+%package -n python3-config2
+Summary:	Python application configuration - highly inspired by `node-config`.
+Provides:	python-config2
+BuildRequires:	python3-devel
+BuildRequires:	python3-setuptools
+BuildRequires:	python3-pip
+%description -n python3-config2
+
+# `config2` [![PyPI version](https://badge.fury.io/py/config2.svg)](https://badge.fury.io/py/config2) [![Build Status](https://travis-ci.com/grimen/python-config2.svg?branch=master)](https://travis-ci.com/grimen/python-config2) [![Coverage Status](https://codecov.io/gh/grimen/python-config2/branch/master/graph/badge.svg)](https://codecov.io/gh/grimen/python-config2)
+
+*Python environment configuration simplified.*
+
+
+## Introduction
+
+**Config2** (for Python) - which is highly inspired by [`node-config`](https://github.com/lorenwest/node-config) - organizes hierarchical configurations for your app deployments.
+
+It lets you define a set of default parameters, and extend them for different deployment environments (development, qa, staging, production, etc.).
+
+Configurations are stored in **configuration files** within your application, and can be overridden and extended by **environment variables**, **command line parameters**, or **external sources**.
+
+This gives your application a consistent configuration interface shared among a growing list of npm modules also using node-config.
+
+**NOTE:** This project is more or less in pair with [`node-config`](https://github.com/lorenwest/node-config) implementation, with exception for some fluff that could be considered too much magic such as deployment specific *multi-instance deployments* which I so far haven't found any good motivation for, and some other questionable advanced features mentioned in the wiki pages.
+
+
+## Project Guidelines
+
+...based on [`node-config`](https://github.com/lorenwest/node-config) project guidelines:
+
+- *Simple* - Get started fast
+- ~~*Powerful* - For multi-node enterprise deployment~~ - excluded because [with power comes responsability](https://en.wikipedia.org/wiki/Principle_of_least_astonishment)
+- *Flexible* - Supporting multiple config file formats
+- *Lightweight* - Small file and memory footprint
+- *Predictable* - Well tested foundation for module and app developers
+
+
+## Install
+
+Install using **pip**:
+
+```sh
+$ pip install config2
+```
+
+
+## Use
+
+**1.** Assuming we have a **python application** project...
+
+```
+some_project
+└── app.py
+```
+
+`app.py` - some app making serious **$$$**
+
+```python
+# business logic
+print('$$$')
+```
+
+
+**2.** Let's add some environment specific **config files**...
+
+```
+some_project
+└── config
+    ├── default.yml
+    ├── development.yml
+    ├── foo.yml
+    └── production.yml
+└── app.py
+```
+
+`default.yml` - with some bogus nested settings shared for all environments (defaults)
+
+```yaml
+a1: DEFAULT 1
+a2:
+    b1: [1, 2, 3]
+    b2:
+        -   foo
+        -   bar
+    b3:
+        c1: 1
+        c2: "DEFAULT 2"
+```
+
+`development.yml` - with some bogus nested settings overriden for `development` environment (overriden)
+
+```yaml
+a2:
+    b2:
+        -   DEV 1
+    b3:
+        c2: "DEV 2"
+some_key_only_for_dev: true
+```
+
+`foo.yml` - with some bogus nested settings overriden for `foo` environment (overriden)
+
+```yaml
+a2:
+    b2:
+        -   FOO 1
+    b3:
+        c2: "FOO 2"
+some_key_only_for_foo: true
+```
+
+`production.yml` - with some bogus nested settings overriden for `production` environment (overriden)
+
+```yaml
+a2:
+    b2:
+        -   PROD 1
+    b3:
+        c2: "PROD 2"
+some_key_only_for_prod: true
+```
+
+
+**3.** Let's now **run the app** using **various environments**...
+
+`$ python app.py`
+
+```python
+from config2.config import config
+
+config.get_env() # => None
+config.get() # => {'a1': 'DEFAULT 1', 'a2': {'b1': [1, 2, 3], 'b2': ['foo', 'bar'], 'b3': {'c1': 1, 'c2': 'DEFAULT 2'}}}
+
+config.a1 # => 'DEFAULT 1'
+config.a2 # => {'b1': [1, 2, 3], 'b2': ['foo', 'bar'], 'b3': {'c1': 1, 'c2': 'DEFAULT 2'}}
+config.a2.b3.c2 # => 'DEFAULT 2'
+
+print('$$$')
+```
+
+`$ ENV=development python app.py`
+
+```python
+from config2.config import config
+
+config.get_env() # => 'development'
+config.get() # => {'a1': 'DEFAULT 1', 'a2': {'b1': [1, 2, 3], 'b2': ['DEV 1'], 'b3': {'c1': 1, 'c2': 'DEV 2'}}, 'some_key_only_for_dev': True}
+
+config.a1 # => 'DEFAULT 1'
+config.a2 # => {'b1': [1, 2, 3], 'b2': ['DEV 1'], 'b3': {'c1': 1, 'c2': 'DEV 2'}}
+config.a2.b3.c2 # => 'DEV was here 2'
+
+config.some_key_only_for_dev # => True
+
+config.some_key_only_for_foo # => AttributeError
+config.some_key_only_for_prod # => AttributeError
+
+print('$$$')
+```
+
+`$ ENV=foo python app.py`
+
+```python
+from config2.config import config
+
+config.get_env() # => 'foo'
+config.get() # => {'a1': 'DEFAULT 1', 'a2': {'b1': [1, 2, 3], 'b2': ['FOO 1'], 'b3': {'c1': 1, 'c2': 'FOO 2'}}, 'some_key_only_for_foo': True}
+
+config.a1 # => 'DEFAULT 1'
+config.a2 # => {'b1': [1, 2, 3], 'b2': ['FOO 1'], 'b3': {'c1': 1, 'c2': 'FOO 2'}}
+config.a2.b3.c2 # => 'FOO was here 2'
+
+config.key_only_for_foo # => True
+
+config.some_key_only_for_dev # => AttributeError
+config.some_key_only_for_prod # => AttributeError
+
+print('$$$')
+```
+
+`$ ENV=production python app.py`
+
+```python
+from config2.config import config
+
+config.get_env() # => 'production'
+config.get() # => {'a1': 'DEFAULT 1', 'a2': {'b1': [1, 2, 3], 'b2': ['PROD 1'], 'b3': {'c1': 1, 'c2': 'PROD 2'}}, 'some_key_only_for_foo': True}
+
+config.a1 # => 'DEFAULT 1'
+config.a2 # => {'b1': [1, 2, 3], 'b2': ['PROD 1'], 'b3': {'c1': 1, 'c2': 'PROD 2'}}
+config.a2.b3.c2 # => 'PROD was here 2'
+
+config.some_key_only_for_prod # => True
+
+config.some_key_only_for_dev # => AttributeError
+config.some_key_only_for_foo # => AttributeError
+
+print('$$$')
+```
+
+etc.
+
+
+**4.** Optionally, let's now introduce custom **config environment variables**...
+
+
+```
+some_project
+└── config
+    ├── custom-environment-variables.yml
+    ├── default.yml
+    ├── development.yml
+    ├── foo.yml
+    └── production.yml
+└── app.py
+```
+
+`custom-environment-variables.yml` - with mappings of config keys to environment variables
+
+```yaml
+a1: A1
+a2:
+    b3:
+        c2: C2
+```
+
+**5.** Let's now **run the app** using **custom environment variables** to override config...
+
+`$ A1=x C2=y python app.py`
+
+```python
+from config2.config import config
+
+config.get_env() # => None
+config.get() # => {'a1': 'x', 'a2': {'b1': [1, 2, 3], 'b2': ['foo', 'bar'], 'b3': {'c1': 1, 'c2': 'y'}}}
+
+config.a1 # => 'x'
+config.a2 # => {'b1': [1, 2, 3], 'b2': ['foo', 'bar'], 'b3': {'c1': 1, 'c2': 'y'}}
+config.a2.b3.c2 # => 'y'
+
+print('$$$')
+```
+
+
+## Test
+
+Clone down source code:
+
+```sh
+$ make install
+```
+
+Run **colorful tests**, with only native environment (dependency sandboxing up to you):
+
+```sh
+$ make test
+```
+
+Run **less colorful tests**, with **multi-environment** (using **tox**):
+
+```sh
+$ make test-tox
+```
+
+
+## About
+
+This project was mainly initiated - in lack of existing alternatives - to be used at our work at **[Markable.ai](https://markable.ai)** to have common code conventions between various programming environments where **Python** (research, CV, AI) and **Node.js** (I/O, APIs, UIs, scripts) currently are most used.
+
+
+## License
+
+Released under the MIT license.
+
+
+
+
+%package help
+Summary:	Development documents and examples for config2
+Provides:	python3-config2-doc
+%description help
+
+# `config2` [![PyPI version](https://badge.fury.io/py/config2.svg)](https://badge.fury.io/py/config2) [![Build Status](https://travis-ci.com/grimen/python-config2.svg?branch=master)](https://travis-ci.com/grimen/python-config2) [![Coverage Status](https://codecov.io/gh/grimen/python-config2/branch/master/graph/badge.svg)](https://codecov.io/gh/grimen/python-config2)
+
+*Python environment configuration simplified.*
+
+
+## Introduction
+
+**Config2** (for Python) - which is highly inspired by [`node-config`](https://github.com/lorenwest/node-config) - organizes hierarchical configurations for your app deployments.
+
+It lets you define a set of default parameters, and extend them for different deployment environments (development, qa, staging, production, etc.).
+
+Configurations are stored in **configuration files** within your application, and can be overridden and extended by **environment variables**, **command line parameters**, or **external sources**.
+
+This gives your application a consistent configuration interface shared among a growing list of npm modules also using node-config.
+
+**NOTE:** This project is more or less in pair with [`node-config`](https://github.com/lorenwest/node-config) implementation, with exception for some fluff that could be considered too much magic such as deployment specific *multi-instance deployments* which I so far haven't found any good motivation for, and some other questionable advanced features mentioned in the wiki pages.
+
+
+## Project Guidelines
+
+...based on [`node-config`](https://github.com/lorenwest/node-config) project guidelines:
+
+- *Simple* - Get started fast
+- ~~*Powerful* - For multi-node enterprise deployment~~ - excluded because [with power comes responsability](https://en.wikipedia.org/wiki/Principle_of_least_astonishment)
+- *Flexible* - Supporting multiple config file formats
+- *Lightweight* - Small file and memory footprint
+- *Predictable* - Well tested foundation for module and app developers
+
+
+## Install
+
+Install using **pip**:
+
+```sh
+$ pip install config2
+```
+
+
+## Use
+
+**1.** Assuming we have a **python application** project...
+
+```
+some_project
+└── app.py
+```
+
+`app.py` - some app making serious **$$$**
+
+```python
+# business logic
+print('$$$')
+```
+
+
+**2.** Let's add some environment specific **config files**...
+
+```
+some_project
+└── config
+    ├── default.yml
+    ├── development.yml
+    ├── foo.yml
+    └── production.yml
+└── app.py
+```
+
+`default.yml` - with some bogus nested settings shared for all environments (defaults)
+
+```yaml
+a1: DEFAULT 1
+a2:
+    b1: [1, 2, 3]
+    b2:
+        -   foo
+        -   bar
+    b3:
+        c1: 1
+        c2: "DEFAULT 2"
+```
+
+`development.yml` - with some bogus nested settings overriden for `development` environment (overriden)
+
+```yaml
+a2:
+    b2:
+        -   DEV 1
+    b3:
+        c2: "DEV 2"
+some_key_only_for_dev: true
+```
+
+`foo.yml` - with some bogus nested settings overriden for `foo` environment (overriden)
+
+```yaml
+a2:
+    b2:
+        -   FOO 1
+    b3:
+        c2: "FOO 2"
+some_key_only_for_foo: true
+```
+
+`production.yml` - with some bogus nested settings overriden for `production` environment (overriden)
+
+```yaml
+a2:
+    b2:
+        -   PROD 1
+    b3:
+        c2: "PROD 2"
+some_key_only_for_prod: true
+```
+
+
+**3.** Let's now **run the app** using **various environments**...
+
+`$ python app.py`
+
+```python
+from config2.config import config
+
+config.get_env() # => None
+config.get() # => {'a1': 'DEFAULT 1', 'a2': {'b1': [1, 2, 3], 'b2': ['foo', 'bar'], 'b3': {'c1': 1, 'c2': 'DEFAULT 2'}}}
+
+config.a1 # => 'DEFAULT 1'
+config.a2 # => {'b1': [1, 2, 3], 'b2': ['foo', 'bar'], 'b3': {'c1': 1, 'c2': 'DEFAULT 2'}}
+config.a2.b3.c2 # => 'DEFAULT 2'
+
+print('$$$')
+```
+
+`$ ENV=development python app.py`
+
+```python
+from config2.config import config
+
+config.get_env() # => 'development'
+config.get() # => {'a1': 'DEFAULT 1', 'a2': {'b1': [1, 2, 3], 'b2': ['DEV 1'], 'b3': {'c1': 1, 'c2': 'DEV 2'}}, 'some_key_only_for_dev': True}
+
+config.a1 # => 'DEFAULT 1'
+config.a2 # => {'b1': [1, 2, 3], 'b2': ['DEV 1'], 'b3': {'c1': 1, 'c2': 'DEV 2'}}
+config.a2.b3.c2 # => 'DEV was here 2'
+
+config.some_key_only_for_dev # => True
+
+config.some_key_only_for_foo # => AttributeError
+config.some_key_only_for_prod # => AttributeError
+
+print('$$$')
+```
+
+`$ ENV=foo python app.py`
+
+```python
+from config2.config import config
+
+config.get_env() # => 'foo'
+config.get() # => {'a1': 'DEFAULT 1', 'a2': {'b1': [1, 2, 3], 'b2': ['FOO 1'], 'b3': {'c1': 1, 'c2': 'FOO 2'}}, 'some_key_only_for_foo': True}
+
+config.a1 # => 'DEFAULT 1'
+config.a2 # => {'b1': [1, 2, 3], 'b2': ['FOO 1'], 'b3': {'c1': 1, 'c2': 'FOO 2'}}
+config.a2.b3.c2 # => 'FOO was here 2'
+
+config.key_only_for_foo # => True
+
+config.some_key_only_for_dev # => AttributeError
+config.some_key_only_for_prod # => AttributeError
+
+print('$$$')
+```
+
+`$ ENV=production python app.py`
+
+```python
+from config2.config import config
+
+config.get_env() # => 'production'
+config.get() # => {'a1': 'DEFAULT 1', 'a2': {'b1': [1, 2, 3], 'b2': ['PROD 1'], 'b3': {'c1': 1, 'c2': 'PROD 2'}}, 'some_key_only_for_foo': True}
+
+config.a1 # => 'DEFAULT 1'
+config.a2 # => {'b1': [1, 2, 3], 'b2': ['PROD 1'], 'b3': {'c1': 1, 'c2': 'PROD 2'}}
+config.a2.b3.c2 # => 'PROD was here 2'
+
+config.some_key_only_for_prod # => True
+
+config.some_key_only_for_dev # => AttributeError
+config.some_key_only_for_foo # => AttributeError
+
+print('$$$')
+```
+
+etc.
+
+
+**4.** Optionally, let's now introduce custom **config environment variables**...
+
+
+```
+some_project
+└── config
+    ├── custom-environment-variables.yml
+    ├── default.yml
+    ├── development.yml
+    ├── foo.yml
+    └── production.yml
+└── app.py
+```
+
+`custom-environment-variables.yml` - with mappings of config keys to environment variables
+
+```yaml
+a1: A1
+a2:
+    b3:
+        c2: C2
+```
+
+**5.** Let's now **run the app** using **custom environment variables** to override config...
+
+`$ A1=x C2=y python app.py`
+
+```python
+from config2.config import config
+
+config.get_env() # => None
+config.get() # => {'a1': 'x', 'a2': {'b1': [1, 2, 3], 'b2': ['foo', 'bar'], 'b3': {'c1': 1, 'c2': 'y'}}}
+
+config.a1 # => 'x'
+config.a2 # => {'b1': [1, 2, 3], 'b2': ['foo', 'bar'], 'b3': {'c1': 1, 'c2': 'y'}}
+config.a2.b3.c2 # => 'y'
+
+print('$$$')
+```
+
+
+## Test
+
+Clone down source code:
+
+```sh
+$ make install
+```
+
+Run **colorful tests**, with only native environment (dependency sandboxing up to you):
+
+```sh
+$ make test
+```
+
+Run **less colorful tests**, with **multi-environment** (using **tox**):
+
+```sh
+$ make test-tox
+```
+
+
+## About
+
+This project was mainly initiated - in lack of existing alternatives - to be used at our work at **[Markable.ai](https://markable.ai)** to have common code conventions between various programming environments where **Python** (research, CV, AI) and **Node.js** (I/O, APIs, UIs, scripts) currently are most used.
+
+
+## License
+
+Released under the MIT license.
+
+
+
+
+%prep
+%autosetup -n config2-0.3.2
+
+%build
+%py3_build
+
+%install
+%py3_install
+install -d -m755 %{buildroot}/%{_pkgdocdir}
+if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi
+if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi
+if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi
+if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi
+pushd %{buildroot}
+if [ -d usr/lib ]; then
+	find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst
+fi
+if [ -d usr/lib64 ]; then
+	find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst
+fi
+if [ -d usr/bin ]; then
+	find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst
+fi
+if [ -d usr/sbin ]; then
+	find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst
+fi
+touch doclist.lst
+if [ -d usr/share/man ]; then
+	find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst
+fi
+popd
+mv %{buildroot}/filelist.lst .
+mv %{buildroot}/doclist.lst .
+
+%files -n python3-config2 -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Tue Apr 11 2023 Python_Bot <Python_Bot@openeuler.org> - 0.3.2-1
+- Package Spec generated
diff --git a/sources b/sources
new file mode 100644
index 0000000..cefdfc9
--- /dev/null
+++ b/sources
@@ -0,0 +1 @@
+8d30d283ad62c3b86c6ad4c9829dfd21  config2-0.3.2.tar.gz