nanoconf 1.0.0__tar.gz

nanoconf-1.0.0/.github/workflows/codeql-analysis.yml

@@ -0,0 +1,45 @@
+name: "CodeQL"
+
+on:
+  push:
+    branches: [master]
+  pull_request:
+    types: [opened, synchronize, reopened]
+    paths-ignore:
+      - "*.md"
+      - ".gitignore"
+
+jobs:
+  analyze:
+    name: CodeQL Analysis
+    runs-on: ubuntu-latest
+
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.11", "3.12"]
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Initialize CodeQL
+        uses: github/codeql-action/init@v2
+        with:
+          languages: ${{ matrix.language }}
+
+      - name: Perform CodeQL Analysis
+        uses: github/codeql-action/analyze@v2
+
+      - name: Setup Python
+        uses: actions/setup-python@v4
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Pre Commit Checks
+        uses: pre-commit/action@v3.0.0
+
+      - name: Unit Tests
+        run: |
+          pip install -U pip .[dev]
+          pytest -v tests/

nanoconf-1.0.0/.github/workflows/python-publish.yml

@@ -0,0 +1,35 @@
+name: PythonPackage
+
+on:
+  push:
+    tags:
+      - "*"
+
+jobs:
+  publish:
+    name: Build and Deploy to PyPi
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        # build/push in lowest support python version
+        python-version: [ "3.11" ]
+
+    steps:
+    - uses: actions/checkout@v4
+
+    - uses: actions/setup-python@v4
+      with:
+        python-version: ${{ matrix.python-version }}
+
+    - name: Setup and Build
+      run: |
+        pip install -U pip .[setup]
+        python -m build
+        python -m twine check dist/*
+
+    - name: Build and publish
+      uses: pypa/gh-action-pypi-publish@v1.8.10
+      with:
+        user: __token__
+        password: ${{ secrets.PYPI_TOKEN }}
+        skip_existing: true

nanoconf-1.0.0/.gitignore

@@ -0,0 +1,5 @@
+venv*
+build/
+*.egg-info/
+__pycache__/
+.vscode/

nanoconf-1.0.0/.pre-commit-config.yaml

@@ -0,0 +1,12 @@
+# configuration for pre-commit git hooks
+repos:
+- repo: https://github.com/psf/black
+  rev: 23.3.0
+  hooks:
+  -   id: black
+- repo: https://github.com/astral-sh/ruff-pre-commit
+  # Ruff version.
+  rev: v0.0.277
+  hooks:
+    - id: ruff
+      args: [--fix, --exit-non-zero-on-fix]

nanoconf-1.0.0/LICENSE

@@ -0,0 +1,3 @@
+Copyright (c) 2023 Jacob Callahan
+
+Do what you want with this repo, but I'm not responsible.

nanoconf-1.0.0/PKG-INFO

@@ -0,0 +1,148 @@
+Metadata-Version: 2.1
+Name: nanoconf
+Version: 1.0.0
+Summary: The tiny opinionated config loader.
+Author-email: Jacob J Callahan <jacob.callahan05@gmail.com>
+Project-URL: Repository, https://github.com/JacobCallahan/nanoconf
+Keywords: nanoconf,config,configuration,settings
+Platform: any
+Classifier: Development Status :: 5 - Production/Stable
+Classifier: Intended Audience :: Developers
+Classifier: Natural Language :: English
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: python-box
+Requires-Dist: pyyaml
+Provides-Extra: dev
+Requires-Dist: black; extra == "dev"
+Requires-Dist: pre-commit; extra == "dev"
+Requires-Dist: pytest; extra == "dev"
+Requires-Dist: ruff; extra == "dev"
+Provides-Extra: setup
+Requires-Dist: build; extra == "setup"
+Requires-Dist: setuptools; extra == "setup"
+Requires-Dist: twine; extra == "setup"
+
+NanoConf
+========
+NanoConf is a tiny, opinionated, and easy to use configuration library for Python. It is designed to be used in small to medium sized projects where a full blown configuration library is overkill.
+
+Installation
+------------
+```bash
+pip install nanoconf
+```
+
+Usage
+-----
+```python
+from nanoconf import NanoConf
+# or if NanoConf if too long of a name
+from nanoconf import NC
+
+# Create a new configuration object
+config = NanoConf("/path/to/config.nconf")
+
+# Use the configuration object
+print(config["key"])
+# Since all values are also loaded as attributes, you can also do
+print(config.key)
+```
+
+Configuration File Format
+-------------------------
+NanoConf uses a simple configuration file format that is easy to read and write.
+Each File is YAML formatted and contains a single top-level dictionary.
+Even though the top-level must be a dictionary, you can nest dictionaries and lists as deep as you want.
+Each config file also must have the .nconf extension. This ensures that NanoConf will only load files that are meant to be configuration files.
+```yaml
+key: value
+test: 1
+overriden: false
+things:
+    - thing1
+    - thing2
+    - thing3
+top:
+    v1: 1
+    middle:
+        v2: 2
+        inner:
+            v3: 3
+            deep:
+                v4: 4
+```
+If you have multiple config files you want to load into a single config object, you can put them all in the same directory and pass that directory to NanoConf.
+NanoConf will automatically place sub-files by their filename as an attribute of the parent file.
+The contents of that file will be accessible as you'd expect under the corresponding filename attribute.
+
+```
+<project root>
+conf_dir
+  |__ cfg1.nconf
+  |__ cfg2.nconf
+  |__ cfg3.nconf
+```
+
+```python
+# load an entire directory
+proj_config = NanoConf("/path/to/conf_dir")
+print(proj_config.cfg1.test)
+```
+
+Or you can import additional files or directories from within any config file by using the `_import` keyword.
+```yaml
+# main.nconf
+_import:
+    - /path/to/project/more_config
+key: value
+test: 1
+```
+
+```
+<project root>
+main.nconf
+more_config
+  |__ subcfg1.nconf
+  |__ subcfg2.nconf
+  |__ subcfg3.nconf
+```
+
+```python
+# loading the main config file will also load the sub-configs
+proj_config = NanoConf("/path/to/project/main.nconf")
+print(proj_config.more_config.subcfg1.test)
+```
+Notice how the directory structure was also maintained in the attribute path. This makes it easier to find the file that a value came from.
+
+Environment Variables
+---------------------
+NanoConf supports environment variables either as overrides to existing values or as additions to the loaded config.
+Envars are evaluated on a per-file basis, so you can have different envars for different config files.
+The way we manage this is by having a special `_envar_prefix` key in the config file.
+**Note:** NanoConf will not modify the case of any environment varable name or value. It is up to you to ensure that the case is correct.
+```yaml
+_envar_prefix: myapp
+key: value
+overrideme: original
+```
+```bash
+export myapp_overrideme=changed
+```
+```python
+config = NanoConf("/path/to/config.nconf")
+print(config.overrideme)
+```
+
+You can also pass complex data structures as JSON strings in environment variables.
+```bash
+export myapp_abc='{"a": 1, "b": 2, "c": 3}'
+```
+```python
+config = NanoConf("/path/to/config.nconf")
+print(config.abc.b)
+```

nanoconf-1.0.0/README.md

@@ -0,0 +1,119 @@
+NanoConf
+========
+NanoConf is a tiny, opinionated, and easy to use configuration library for Python. It is designed to be used in small to medium sized projects where a full blown configuration library is overkill.
+
+Installation
+------------
+```bash
+pip install nanoconf
+```
+
+Usage
+-----
+```python
+from nanoconf import NanoConf
+# or if NanoConf if too long of a name
+from nanoconf import NC
+
+# Create a new configuration object
+config = NanoConf("/path/to/config.nconf")
+
+# Use the configuration object
+print(config["key"])
+# Since all values are also loaded as attributes, you can also do
+print(config.key)
+```
+
+Configuration File Format
+-------------------------
+NanoConf uses a simple configuration file format that is easy to read and write.
+Each File is YAML formatted and contains a single top-level dictionary.
+Even though the top-level must be a dictionary, you can nest dictionaries and lists as deep as you want.
+Each config file also must have the .nconf extension. This ensures that NanoConf will only load files that are meant to be configuration files.
+```yaml
+key: value
+test: 1
+overriden: false
+things:
+    - thing1
+    - thing2
+    - thing3
+top:
+    v1: 1
+    middle:
+        v2: 2
+        inner:
+            v3: 3
+            deep:
+                v4: 4
+```
+If you have multiple config files you want to load into a single config object, you can put them all in the same directory and pass that directory to NanoConf.
+NanoConf will automatically place sub-files by their filename as an attribute of the parent file.
+The contents of that file will be accessible as you'd expect under the corresponding filename attribute.
+
+```
+<project root>
+conf_dir
+  |__ cfg1.nconf
+  |__ cfg2.nconf
+  |__ cfg3.nconf
+```
+
+```python
+# load an entire directory
+proj_config = NanoConf("/path/to/conf_dir")
+print(proj_config.cfg1.test)
+```
+
+Or you can import additional files or directories from within any config file by using the `_import` keyword.
+```yaml
+# main.nconf
+_import:
+    - /path/to/project/more_config
+key: value
+test: 1
+```
+
+```
+<project root>
+main.nconf
+more_config
+  |__ subcfg1.nconf
+  |__ subcfg2.nconf
+  |__ subcfg3.nconf
+```
+
+```python
+# loading the main config file will also load the sub-configs
+proj_config = NanoConf("/path/to/project/main.nconf")
+print(proj_config.more_config.subcfg1.test)
+```
+Notice how the directory structure was also maintained in the attribute path. This makes it easier to find the file that a value came from.
+
+Environment Variables
+---------------------
+NanoConf supports environment variables either as overrides to existing values or as additions to the loaded config.
+Envars are evaluated on a per-file basis, so you can have different envars for different config files.
+The way we manage this is by having a special `_envar_prefix` key in the config file.
+**Note:** NanoConf will not modify the case of any environment varable name or value. It is up to you to ensure that the case is correct.
+```yaml
+_envar_prefix: myapp
+key: value
+overrideme: original
+```
+```bash
+export myapp_overrideme=changed
+```
+```python
+config = NanoConf("/path/to/config.nconf")
+print(config.overrideme)
+```
+
+You can also pass complex data structures as JSON strings in environment variables.
+```bash
+export myapp_abc='{"a": 1, "b": 2, "c": 3}'
+```
+```python
+config = NanoConf("/path/to/config.nconf")
+print(config.abc.b)
+```

nanoconf-1.0.0/nanoconf/__init__.py

@@ -0,0 +1,3 @@
+from nanoconf.nanoconf import NanoConf
+
+NC = NanoConf

nanoconf-1.0.0/nanoconf/nanoconf.py

@@ -0,0 +1,47 @@
+import contextlib
+import json
+import os
+from pathlib import Path
+
+from box import Box
+import yaml
+
+
+class NanoConf:
+    def __init__(self, cfg_path="."):
+        self._cfg_path = Path(cfg_path)
+        self._name = self._cfg_path.stem
+        if self._cfg_path.is_dir():
+            for sub in self._cfg_path.glob("*.nconf"):
+                new_conf = NanoConf(sub)
+                setattr(self, new_conf._name, new_conf)
+        elif self._cfg_path.is_file() and self._cfg_path.suffix == ".nconf":
+            self._load_config()
+            self._pull_envars()
+
+    def _load_config(self):
+        cfg_dict = yaml.load(self._cfg_path.read_text(), Loader=yaml.SafeLoader)
+        for sub_import in cfg_dict.pop("_import", []):
+            new_conf = NanoConf(
+                self._cfg_path / sub_import
+                if self._cfg_path.is_dir()
+                else self._cfg_path.parent / sub_import
+            )
+            setattr(self, new_conf._name, new_conf)
+        self.__dict__.update(Box(cfg_dict))
+
+    def _pull_envars(self):
+        if getattr(self, "_envar_prefix", ""):
+            for key, val in os.environ.items():
+                if key.startswith(self._envar_prefix):
+                    key_name = key.replace(f"{self._envar_prefix}_", "")
+                    with contextlib.suppress(json.decoder.JSONDecodeError):
+                        val = Box(json.loads(val))  # noqa: PLW2901
+                    self.__dict__[key_name] = val
+
+    def __repr__(self):
+        return (
+            f"<NanoConf {self._name}.("
+            + ", ".join(filter(lambda x: not x.startswith("_"), self.__dict__.keys()))
+            + ")>"
+        )

nanoconf-1.0.0/nanoconf.egg-info/PKG-INFO

@@ -0,0 +1,148 @@
+Metadata-Version: 2.1
+Name: nanoconf
+Version: 1.0.0
+Summary: The tiny opinionated config loader.
+Author-email: Jacob J Callahan <jacob.callahan05@gmail.com>
+Project-URL: Repository, https://github.com/JacobCallahan/nanoconf
+Keywords: nanoconf,config,configuration,settings
+Platform: any
+Classifier: Development Status :: 5 - Production/Stable
+Classifier: Intended Audience :: Developers
+Classifier: Natural Language :: English
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: python-box
+Requires-Dist: pyyaml
+Provides-Extra: dev
+Requires-Dist: black; extra == "dev"
+Requires-Dist: pre-commit; extra == "dev"
+Requires-Dist: pytest; extra == "dev"
+Requires-Dist: ruff; extra == "dev"
+Provides-Extra: setup
+Requires-Dist: build; extra == "setup"
+Requires-Dist: setuptools; extra == "setup"
+Requires-Dist: twine; extra == "setup"
+
+NanoConf
+========
+NanoConf is a tiny, opinionated, and easy to use configuration library for Python. It is designed to be used in small to medium sized projects where a full blown configuration library is overkill.
+
+Installation
+------------
+```bash
+pip install nanoconf
+```
+
+Usage
+-----
+```python
+from nanoconf import NanoConf
+# or if NanoConf if too long of a name
+from nanoconf import NC
+
+# Create a new configuration object
+config = NanoConf("/path/to/config.nconf")
+
+# Use the configuration object
+print(config["key"])
+# Since all values are also loaded as attributes, you can also do
+print(config.key)
+```
+
+Configuration File Format
+-------------------------
+NanoConf uses a simple configuration file format that is easy to read and write.
+Each File is YAML formatted and contains a single top-level dictionary.
+Even though the top-level must be a dictionary, you can nest dictionaries and lists as deep as you want.
+Each config file also must have the .nconf extension. This ensures that NanoConf will only load files that are meant to be configuration files.
+```yaml
+key: value
+test: 1
+overriden: false
+things:
+    - thing1
+    - thing2
+    - thing3
+top:
+    v1: 1
+    middle:
+        v2: 2
+        inner:
+            v3: 3
+            deep:
+                v4: 4
+```
+If you have multiple config files you want to load into a single config object, you can put them all in the same directory and pass that directory to NanoConf.
+NanoConf will automatically place sub-files by their filename as an attribute of the parent file.
+The contents of that file will be accessible as you'd expect under the corresponding filename attribute.
+
+```
+<project root>
+conf_dir
+  |__ cfg1.nconf
+  |__ cfg2.nconf
+  |__ cfg3.nconf
+```
+
+```python
+# load an entire directory
+proj_config = NanoConf("/path/to/conf_dir")
+print(proj_config.cfg1.test)
+```
+
+Or you can import additional files or directories from within any config file by using the `_import` keyword.
+```yaml
+# main.nconf
+_import:
+    - /path/to/project/more_config
+key: value
+test: 1
+```
+
+```
+<project root>
+main.nconf
+more_config
+  |__ subcfg1.nconf
+  |__ subcfg2.nconf
+  |__ subcfg3.nconf
+```
+
+```python
+# loading the main config file will also load the sub-configs
+proj_config = NanoConf("/path/to/project/main.nconf")
+print(proj_config.more_config.subcfg1.test)
+```
+Notice how the directory structure was also maintained in the attribute path. This makes it easier to find the file that a value came from.
+
+Environment Variables
+---------------------
+NanoConf supports environment variables either as overrides to existing values or as additions to the loaded config.
+Envars are evaluated on a per-file basis, so you can have different envars for different config files.
+The way we manage this is by having a special `_envar_prefix` key in the config file.
+**Note:** NanoConf will not modify the case of any environment varable name or value. It is up to you to ensure that the case is correct.
+```yaml
+_envar_prefix: myapp
+key: value
+overrideme: original
+```
+```bash
+export myapp_overrideme=changed
+```
+```python
+config = NanoConf("/path/to/config.nconf")
+print(config.overrideme)
+```
+
+You can also pass complex data structures as JSON strings in environment variables.
+```bash
+export myapp_abc='{"a": 1, "b": 2, "c": 3}'
+```
+```python
+config = NanoConf("/path/to/config.nconf")
+print(config.abc.b)
+```

nanoconf-1.0.0/nanoconf.egg-info/SOURCES.txt

@@ -0,0 +1,23 @@
+.gitignore
+.pre-commit-config.yaml
+LICENSE
+README.md
+pyproject.toml
+.github/workflows/codeql-analysis.yml
+.github/workflows/python-publish.yml
+nanoconf/__init__.py
+nanoconf/nanoconf.py
+nanoconf.egg-info/PKG-INFO
+nanoconf.egg-info/SOURCES.txt
+nanoconf.egg-info/dependency_links.txt
+nanoconf.egg-info/not-zip-safe
+nanoconf.egg-info/requires.txt
+nanoconf.egg-info/top_level.txt
+tests/test_nanoconf.py
+tests/data/nested.nconf
+tests/data/simple.nconf
+tests/data/animals/dog.nconf
+tests/data/animals/elephant.nconf
+tests/data/animals/lion.nconf
+tests/data/animals/panda.nconf
+tests/data/animals/penguin.nconf

nanoconf-1.0.0/nanoconf.egg-info/dependency_links.txt

@@ -0,0 +1 @@
+

nanoconf-1.0.0/nanoconf.egg-info/not-zip-safe

@@ -0,0 +1 @@
+

nanoconf-1.0.0/nanoconf.egg-info/requires.txt

@@ -0,0 +1,13 @@
+python-box
+pyyaml
+
+[dev]
+black
+pre-commit
+pytest
+ruff
+
+[setup]
+build
+setuptools
+twine

nanoconf-1.0.0/nanoconf.egg-info/top_level.txt

@@ -0,0 +1 @@
+nanoconf

nanoconf-1.0.0/pyproject.toml

@@ -0,0 +1,127 @@
+[project]
+name = "nanoconf"
+description = "The tiny opinionated config loader."
+readme = "README.md"
+requires-python = ">=3.11"
+keywords = ["nanoconf", "config", "configuration", "settings"]
+authors = [
+    {name = "Jacob J Callahan", email = "jacob.callahan05@gmail.com"}
+]
+classifiers = [
+    "Development Status :: 5 - Production/Stable",
+    "Intended Audience :: Developers",
+    "Natural Language :: English",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+]
+dependencies = [
+    "python-box",
+    "pyyaml",
+]
+dynamic = ["version"]  # dynamic fields to update on build - version via setuptools_scm
+
+[project.urls]
+Repository = "https://github.com/JacobCallahan/nanoconf"
+
+[build-system]
+requires = ["setuptools", "setuptools-scm[toml]", "wheel"]
+build-backend = "setuptools.build_meta"
+
+[tool.setuptools]
+platforms = ["any"]
+zip-safe = false
+include-package-data = true
+
+[tool.setuptools.packages.find]
+include = ["nanoconf"]
+
+[tool.setuptools_scm]  # same as use_scm_version=True in setup.py
+
+[project.optional-dependencies]
+dev = [
+    "black",
+    "pre-commit",
+    "pytest",
+    "ruff",
+]
+setup = [
+    "build",
+    "setuptools",
+    "twine",
+]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+addopts = ["-v", "-l", "--color=yes", "--code-highlight=yes"]
+
+[tool.black]
+line-length = 100
+target-version = ["py311"]
+include = '\.pyi?$'
+exclude = '''
+/(
+    \.git
+  | \.venv
+  | build
+  | dist
+  | tests/data
+)/
+'''
+
+[tool.ruff]
+target-version = "py311"
+fixable = ["ALL"]
+
+select = [
+    "B", # bugbear
+    "C", # complexity
+    "C4", # flake8-comprehensions
+    "COM818", # Trailing comma on bare tuple prohibited
+    "E", # pycodestyle
+    "F", # pyflakes/autoflake
+    "G", # flake8-logging-format
+    "I", # isort
+    "ISC001", # Implicitly concatenated string literals on one License
+    "N",
+    "PERF", # Perflint rules
+    "PGH004", # Use specific rule codes when using noqa
+    "PLC", # pylint
+    "PLE", # pylint
+    "PLR", # pylint
+    "PLW", # pylint
+    "PTH", # Use pathlib
+    "RUF", # Ruff-specific rules
+    "S", # flake8-bandit
+    "SIM", #flake8-simplify
+    "T100", # leftover breakpoint()
+    "T20", # leftover print()
+    "TRY004", # Prefer TypeError exception for invalid type
+    "TRY200", # Use raise from to specify exception cause
+    "TRY302", # Remove exception handler; error is immediately re-raised
+    "PL", # pylint
+    "UP", # pyupgrade
+    "W", # pycodestyle
+]
+
+ignore = [
+    "ANN", # flake8-annotations
+    "E501", # line too long
+    "RUF012", # Mutable class attributes should be annotated with typing.ClassVar
+]
+
+[tool.ruff.per-file-ignores]
+"tests/test_nanoconf.py" = ["S101", "PLR2004"]
+
+[tool.ruff.flake8-pytest-style]
+fixture-parentheses = false
+
+[tool.ruff.isort]
+force-sort-within-sections = true
+known-first-party = [
+    "nanoconf",
+]
+combine-as-imports = true
+
+[tool.ruff.mccabe]
+max-complexity = 25

nanoconf-1.0.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

nanoconf-1.0.0/tests/data/animals/dog.nconf

@@ -0,0 +1,6 @@
+_envar_prefix: testdog
+name: Dog
+species: Canis lupus familiaris
+habitat: Domesticated
+diet: Omnivore
+weight: 5-70 kg

nanoconf-1.0.0/tests/data/animals/elephant.nconf

@@ -0,0 +1,5 @@
+name: Elephant
+species: Loxodonta africana
+habitat: Savannas, forests, and deserts
+diet: Herbivore
+weight: 2,268-5,443 kg

nanoconf-1.0.0/tests/data/animals/lion.nconf

@@ -0,0 +1,5 @@
+name: Lion
+species: Panthera leo
+habitat: Grasslands, savannas, and forests
+diet: Carnivore
+weight: 190-260 kg

nanoconf-1.0.0/tests/data/animals/panda.nconf

@@ -0,0 +1,5 @@
+name: Panda
+species: Ailuropoda melanoleuca
+habitat: Temperate forests of China
+diet: Herbivore
+weight: 70-125 kg

nanoconf-1.0.0/tests/data/animals/penguin.nconf

@@ -0,0 +1,5 @@
+name: Penguin
+species: Spheniscidae
+habitat: Antarctica, southern Africa, South America, and New Zealand
+diet: Carnivore
+weight: 1-5 kg

nanoconf-1.0.0/tests/data/nested.nconf

@@ -0,0 +1,9 @@
+_import:
+  - animals
+test: value
+top:
+  v1: 1
+  middle:
+    v2: 2
+    lowest:
+      v3: 3

nanoconf-1.0.0/tests/data/simple.nconf

@@ -0,0 +1,8 @@
+_envar_prefix: simple
+key: value
+test: 1
+overriden: False
+things:
+    - thing1
+    - thing2
+    - thing3

nanoconf-1.0.0/tests/test_nanoconf.py

@@ -0,0 +1,54 @@
+import os
+
+from box import Box, BoxList
+import pytest
+
+from nanoconf import NC
+
+
+@pytest.fixture
+def set_envars(request):
+    if isinstance(request.param, list):
+        for pair in request.param:
+            os.environ[pair[0]] = pair[1]
+        yield
+        for pair in request.param:
+            del os.environ[pair[0]]
+    else:
+        os.environ[request.param[0]] = request.param[1]
+        yield
+        del os.environ[request.param[0]]
+
+
+@pytest.mark.parametrize("set_envars", [("simple_overriden", "True")], indirect=True)
+def test_simple(set_envars):
+    nconf = NC("tests/data/simple.nconf")
+    assert nconf._name == "simple"
+    assert nconf._envar_prefix == "simple"
+    assert isinstance(nconf.things, BoxList)
+    assert len(nconf.things) == 3
+    assert nconf.overriden == "True"
+
+
+@pytest.mark.parametrize("set_envars", [("simple_overriden", '{"a": 1, "b": 2}')], indirect=True)
+def test_json_envar(set_envars):
+    nconf = NC("tests/data/simple.nconf")
+    assert isinstance(nconf.overriden, Box)
+    assert nconf.overriden.a == 1
+    assert nconf.overriden.b == 2
+
+
+def test_nested():
+    nconf = NC("tests/data/nested.nconf")
+    assert nconf._name == "nested"
+    assert nconf.top.v1 == 1
+    assert nconf.top.middle.v2 == 2
+    assert nconf.top.middle.lowest.v3 == 3
+    assert nconf.animals.panda.diet == "Herbivore"
+    assert all([nconf.animals.dog, nconf.animals.lion, nconf.animals.penguin])
+
+
+@pytest.mark.parametrize("set_envars", [("testdog_diet", "Treats!")], indirect=True)
+def test_nested_envar(set_envars):
+    nconf = NC("tests/data/nested.nconf")
+    assert nconf.animals.dog.diet == "Treats!"