upref 2.0.1__tar.gz → 2.2.0__tar.gz

upref-2.2.0/.gitattributes

@@ -0,0 +1,3 @@
+*.bat text eol=crlf
+*.cmd text eol=crlf
+*.py text eol=lf

upref-2.2.0/CHANGELOG.md

@@ -0,0 +1,92 @@
+# Changelog
+
+## 2.2.0 - 2026-09-26
+
+### Added
+
+- Ten runnable user-preference scenarios: first-run setup, Apply/Cancel, resets,
+  recent documents, window geometry, account settings, CLI session overrides,
+  portable JSON import/export, backup/restore, and legacy migration preview.
+  The catalog now contains 26 examples, with a dedicated walkthrough guide.
+- Explicit `source_format="auto" | "raw" | "descriptors"` selection and
+  `dry_run=True` previews for legacy migration, retaining the default heuristic
+  and target preflight checks.
+- Hypothesis properties for persistence, copying, merging, and failed writes.
+- Native wxPython integration scenarios with process timeouts and a dedicated
+  Windows CI job; minimum runtime dependency testing on Python 3.10.
+- Functional installed-wheel and resource checks in CI and release automation.
+- A release-based deprecation schedule: v1 wrappers remain through 2.x and are
+  scheduled for removal in 3.0. Explicit migration remains supported.
+
+### Fixed
+
+- Preserve Unicode NEL (U+0085) in YAML keys and values instead of folding it
+  into a space; ordinary Unicode remains readable.
+- Reject non-scalar YAML keys carrying scalar tags with `ConfigFormatError`
+  and a source location instead of leaking a `TypeError`.
+- Reject null characters in configuration directories during construction.
+- Normalize string subclass keys to plain strings, preserving their underlying
+  text so string-backed enum keys can be saved. Scalar enum values still need
+  explicit conversion; normalized key collisions are rejected.
+- Measure branch coverage as well as statement coverage, retaining the 100%
+  gate and covering application reuse and pre-write failures.
+- Exercise POSIX and Windows permission branches on every platform so the
+  coverage gate behaves consistently on Linux, macOS, and Windows.
+
+### Compatibility
+
+- Python 3.10 and later remain supported, with no new runtime dependency.
+- Existing migration calls retain their behavior; format selection and previews
+  are optional. Deprecated v1 wrappers remain available throughout 2.x.
+- Malformed YAML keys and invalid configuration directories now consistently
+  raise the documented configuration exceptions. Duplicate normalized keys are
+  rejected instead of silently replacing an existing value.
+
+## 2.1.0
+
+### Added
+
+- Public `parse_bool` parser for yes/no, true/false, on/off, y/n, and 1/0 input.
+- Keyword-only `Field.formatter` to format current values for terminal display
+  and GUI prefill, including JSON lists and mappings.
+- Opt-in `TTYPrompter(keep_current=True)` to retain a non-secret current value
+  with Enter, while still parsing and validating it.
+- Nine runnable examples covering portable storage, boolean input, editing,
+  GUI collection, custom interfaces, nested settings, application validation,
+  schema upgrades, and error handling; 16 examples are now available.
+- Practical recipes, troubleshooting, and a documented code review.
+
+### Fixed
+
+- Reject duplicate explicit YAML keys with source locations while preserving
+  YAML merge defaults and explicit overrides.
+- Report invalid YAML scalar construction and excessive recursion during
+  parsing, normalization, or serialization as `ConfigFormatError`.
+- Preserve the documented `ConfigReadError` behavior for file inspection
+  failures in `ConfigStore.exists()`.
+- Reject malformed fields, schemas, and custom prompter contracts early.
+- Clarify required/optional input and cancellation in the bundled interfaces.
+- Include examples, documentation, scripts, and pytest configuration in source
+  distributions, with an archive-content check in CI.
+- Align Python checkout line endings with the formatter on Windows.
+
+### Compatibility
+
+- Files with duplicate explicit YAML keys must be corrected before loading.
+  Previous releases silently selected the last value. YAML merge directives
+  remain supported.
+- Invalid `Field` definitions now raise `TypeError` at construction. Custom
+  prompter methods must be callable, and `ask()` must return text or `None`.
+- Existing positional `Field` arguments remain supported. The formatter and
+  terminal value-reuse option are optional; blank input is still submitted
+  literally by default. Secret current values are never formatted or reused.
+- Python 3.10 and later remain supported. No new runtime dependency is required.
+
+### Validation
+
+- 230 tests passed locally on Windows with 100% statement coverage; three
+  platform-specific tests were skipped.
+- Ruff, strict mypy, Sphinx, source-distribution tests, wheel persistence smoke
+  checks, and distribution metadata validation passed.
+- GUI contracts use a wxPython substitute in the tests; actual window rendering
+  was not verified in the local environment.

upref-2.2.0/MANIFEST.in

@@ -0,0 +1,7 @@
+include pytest.ini make.bat .gitattributes
+include CHANGELOG.md
+recursive-include examples *.py *.md
+recursive-include scripts *.py *.ps1
+recursive-include tests *.py
+recursive-include docs *.rst *.md *.py *.css *.png
+prune docs/_build

{upref-2.0.1 → upref-2.2.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: upref
-Version: 2.0.1
+Version: 2.2.0
 Summary: Small, explicit, and safe per-user configuration storage
 Author: Florent Tournois
 License-Expression: MIT
@@ -25,6 +25,7 @@ Requires-Dist: PyYAML>=6.0
 Provides-Extra: gui
 Requires-Dist: wxPython>=4.2; extra == "gui"
 Provides-Extra: test
+Requires-Dist: hypothesis>=6.100; extra == "test"
 Requires-Dist: mypy>=2; extra == "test"
 Requires-Dist: pytest>=8; extra == "test"
 Requires-Dist: pytest-cov>=5; extra == "test"
@@ -36,6 +37,7 @@ Requires-Dist: sphinx>=7; extra == "docs"
 Requires-Dist: sphinx-rtd-theme>=2; extra == "docs"
 Provides-Extra: dev
 Requires-Dist: build>=1.2; extra == "dev"
+Requires-Dist: hypothesis>=6.100; extra == "dev"
 Requires-Dist: mypy>=2; extra == "dev"
 Requires-Dist: myst-parser>=2; extra == "dev"
 Requires-Dist: pytest>=8; extra == "dev"
@@ -113,6 +115,9 @@ config = store.update({
 ```
 
 Nested dictionaries are merged. Lists and scalar values are replaced.
+Duplicate explicit YAML keys are rejected with a file location instead of
+silently discarding earlier values. YAML merge directives may still provide
+defaults that explicit keys override.
 `store.exists()` checks for the file, while `store.delete()` removes only that
 file and reports whether it existed.
 
@@ -192,6 +197,32 @@ In `missing` mode, absent values, `None`, and required empty strings are
 requested. `False` and `0` already count as values. Use `mode="all"` to ask
 for every field, or `interface="gui"` after installing `upref[gui]`.
 
+For boolean input, use the public `parse_bool` parser; it accepts `yes/no`,
+`true/false`, `on/off`, `y/n`, and `1/0`, ignoring case and whitespace.
+Python's `bool("false")` returns `True` and is unsuitable for this purpose.
+
+```python
+from upref import Field, collect, parse_bool
+from upref.tty import TTYPrompter
+
+values = collect(
+    {"enabled": Field("Enable notifications", parser=parse_bool)},
+    initial={"enabled": False},
+    interface=TTYPrompter(keep_current=True),
+    mode="all",
+)
+```
+
+With `keep_current=True`, Enter reuses a current non-secret value and runs it
+through the parser and validator again. By default, blank input remains blank.
+For structured input, pair a parser with a compatible keyword-only formatter:
+`Field("Tags", parser=json.loads, formatter=json.dumps)` (after `import json`).
+The GUI uses this formatter to prefill existing values correctly.
+
+`collect` validates newly entered values. Existing values skipped in `missing`
+mode are not passed through field validators; validate application constraints
+after loading when stored files may have been edited manually.
+
 ## Storage guarantees and limits
 
 Upref writes UTF-8 YAML to a temporary file in the destination directory,
@@ -216,10 +247,18 @@ store = ConfigStore("my-application")
 config = store.import_legacy("my_personnal_data")
 ```
 
+For ambiguous files, choose ``source_format="raw"`` to retain the entire
+mapping, or ``source_format="descriptors"`` to extract v1 values explicitly.
+Add ``dry_run=True`` to inspect the conversion without writing. Previewing
+still performs source and target preflight checks. The default ``"auto"``
+format retains the historical heuristic.
+
 The source file is left untouched, and using it as the v2 target is rejected.
 Migration checks for an existing v2 file unless `overwrite=True` is passed;
 because this preflight check is not locked, applications with concurrent
 writers must coordinate the migration externally.
+Deprecated v1 wrappers remain available throughout 2.x and are scheduled for
+removal in 3.0; explicit file migration remains supported.
 
 ## Security
 
@@ -233,19 +272,43 @@ reference in Upref.
 ## Documentation and examples
 
 The complete user guide and API reference are available on
-[Read the Docs](https://upref.readthedocs.io/). Runnable examples live in
-[`examples`](https://github.com/IIXIXII/upref/tree/master/examples):
-
-- `basic_store.py` covers a save/load cycle;
-- `defaults_and_update.py` covers defaults, recursive updates, and deletion;
-- `project_variables.py` collects required variables for one project;
-- `environment_profiles.py` selects profiles with temporary environment overrides;
-- `multiple_projects.py` stores independent settings for related projects;
-- `tty_collection.py` collects missing values without a GUI;
-- `migrate_v1.py` imports a historical configuration.
-
-Except for the migration example, these programs use the platform's per-user
-configuration directory. They do not create files in the repository.
+[Read the Docs](https://upref.readthedocs.io/). The
+[example catalog](docs/examples.rst) lists 26 runnable programs by difficulty,
+input method, and file effects. Start with these:
+
+| Level | Example | What it demonstrates |
+| --- | --- | --- |
+| Simple | `portable_store.py` | Defaults, save/load, and updates in a temporary directory |
+| Simple | `boolean_collection.py` | Boolean parsing, optional input, and cancellation |
+| Simple | `first_run_preferences.py` | Initial user setup and reuse on the next startup |
+| Intermediate | `apply_preferences.py` | Edit a draft, then confirm or discard changes |
+| Intermediate | `reset_preferences.py` | Restore one preference, a section, or all defaults |
+| Intermediate | `session_overrides.py` | CLI overrides with explicit `--remember` persistence |
+| Advanced | `import_export_preferences.py` | Validated preference transfer with local history retained |
+| Intermediate | `edit_settings.py` | Enter to keep values and editable JSON lists |
+| Intermediate | `gui_collection.py` | GUI ownership, formatted prefill, and cancellation |
+| Intermediate | `handle_errors.py` | Reporting malformed YAML while retaining the file |
+| Advanced | `nested_collection.py` | Editing a subsection before an explicit save |
+| Advanced | `custom_interface.py` | A deterministic custom prompter with validation retries |
+| Advanced | `typed_settings.py` | Application validation with a dataclass |
+| Advanced | `schema_upgrade.py` | An idempotent application schema migration |
+
+The new demonstrations use memory or automatically cleaned temporary
+directories. Earlier examples that demonstrate persistent settings use named
+per-user directories; their effects are listed in the catalog. Run examples
+from an installed checkout (`python -m pip install -e .`):
+
+```console
+python examples/portable_store.py
+python examples/custom_interface.py
+```
+
+The [user preference walkthroughs](docs/user_preferences.rst) also cover recent
+documents, window geometry, multiple accounts, backup/restore, and previewing
+legacy migration. Every scenario in that guide uses temporary files.
+
+See also the [troubleshooting guide](docs/troubleshooting.rst) and the
+[code review and compatibility notes](docs/review.rst).
 
 ## Development with `.venv`
 

{upref-2.0.1 → upref-2.2.0}/README.md

@@ -63,6 +63,9 @@ config = store.update({
 ```
 
 Nested dictionaries are merged. Lists and scalar values are replaced.
+Duplicate explicit YAML keys are rejected with a file location instead of
+silently discarding earlier values. YAML merge directives may still provide
+defaults that explicit keys override.
 `store.exists()` checks for the file, while `store.delete()` removes only that
 file and reports whether it existed.
 
@@ -142,6 +145,32 @@ In `missing` mode, absent values, `None`, and required empty strings are
 requested. `False` and `0` already count as values. Use `mode="all"` to ask
 for every field, or `interface="gui"` after installing `upref[gui]`.
 
+For boolean input, use the public `parse_bool` parser; it accepts `yes/no`,
+`true/false`, `on/off`, `y/n`, and `1/0`, ignoring case and whitespace.
+Python's `bool("false")` returns `True` and is unsuitable for this purpose.
+
+```python
+from upref import Field, collect, parse_bool
+from upref.tty import TTYPrompter
+
+values = collect(
+    {"enabled": Field("Enable notifications", parser=parse_bool)},
+    initial={"enabled": False},
+    interface=TTYPrompter(keep_current=True),
+    mode="all",
+)
+```
+
+With `keep_current=True`, Enter reuses a current non-secret value and runs it
+through the parser and validator again. By default, blank input remains blank.
+For structured input, pair a parser with a compatible keyword-only formatter:
+`Field("Tags", parser=json.loads, formatter=json.dumps)` (after `import json`).
+The GUI uses this formatter to prefill existing values correctly.
+
+`collect` validates newly entered values. Existing values skipped in `missing`
+mode are not passed through field validators; validate application constraints
+after loading when stored files may have been edited manually.
+
 ## Storage guarantees and limits
 
 Upref writes UTF-8 YAML to a temporary file in the destination directory,
@@ -166,10 +195,18 @@ store = ConfigStore("my-application")
 config = store.import_legacy("my_personnal_data")
 ```
 
+For ambiguous files, choose ``source_format="raw"`` to retain the entire
+mapping, or ``source_format="descriptors"`` to extract v1 values explicitly.
+Add ``dry_run=True`` to inspect the conversion without writing. Previewing
+still performs source and target preflight checks. The default ``"auto"``
+format retains the historical heuristic.
+
 The source file is left untouched, and using it as the v2 target is rejected.
 Migration checks for an existing v2 file unless `overwrite=True` is passed;
 because this preflight check is not locked, applications with concurrent
 writers must coordinate the migration externally.
+Deprecated v1 wrappers remain available throughout 2.x and are scheduled for
+removal in 3.0; explicit file migration remains supported.
 
 ## Security
 
@@ -183,19 +220,43 @@ reference in Upref.
 ## Documentation and examples
 
 The complete user guide and API reference are available on
-[Read the Docs](https://upref.readthedocs.io/). Runnable examples live in
-[`examples`](https://github.com/IIXIXII/upref/tree/master/examples):
-
-- `basic_store.py` covers a save/load cycle;
-- `defaults_and_update.py` covers defaults, recursive updates, and deletion;
-- `project_variables.py` collects required variables for one project;
-- `environment_profiles.py` selects profiles with temporary environment overrides;
-- `multiple_projects.py` stores independent settings for related projects;
-- `tty_collection.py` collects missing values without a GUI;
-- `migrate_v1.py` imports a historical configuration.
-
-Except for the migration example, these programs use the platform's per-user
-configuration directory. They do not create files in the repository.
+[Read the Docs](https://upref.readthedocs.io/). The
+[example catalog](docs/examples.rst) lists 26 runnable programs by difficulty,
+input method, and file effects. Start with these:
+
+| Level | Example | What it demonstrates |
+| --- | --- | --- |
+| Simple | `portable_store.py` | Defaults, save/load, and updates in a temporary directory |
+| Simple | `boolean_collection.py` | Boolean parsing, optional input, and cancellation |
+| Simple | `first_run_preferences.py` | Initial user setup and reuse on the next startup |
+| Intermediate | `apply_preferences.py` | Edit a draft, then confirm or discard changes |
+| Intermediate | `reset_preferences.py` | Restore one preference, a section, or all defaults |
+| Intermediate | `session_overrides.py` | CLI overrides with explicit `--remember` persistence |
+| Advanced | `import_export_preferences.py` | Validated preference transfer with local history retained |
+| Intermediate | `edit_settings.py` | Enter to keep values and editable JSON lists |
+| Intermediate | `gui_collection.py` | GUI ownership, formatted prefill, and cancellation |
+| Intermediate | `handle_errors.py` | Reporting malformed YAML while retaining the file |
+| Advanced | `nested_collection.py` | Editing a subsection before an explicit save |
+| Advanced | `custom_interface.py` | A deterministic custom prompter with validation retries |
+| Advanced | `typed_settings.py` | Application validation with a dataclass |
+| Advanced | `schema_upgrade.py` | An idempotent application schema migration |
+
+The new demonstrations use memory or automatically cleaned temporary
+directories. Earlier examples that demonstrate persistent settings use named
+per-user directories; their effects are listed in the catalog. Run examples
+from an installed checkout (`python -m pip install -e .`):
+
+```console
+python examples/portable_store.py
+python examples/custom_interface.py
+```
+
+The [user preference walkthroughs](docs/user_preferences.rst) also cover recent
+documents, window geometry, multiple accounts, backup/restore, and previewing
+legacy migration. Every scenario in that guide uses temporary files.
+
+See also the [troubleshooting guide](docs/troubleshooting.rst) and the
+[code review and compatibility notes](docs/review.rst).
 
 ## Development with `.venv`
 

upref-2.2.0/docs/api.rst

@@ -0,0 +1,110 @@
+.. _api-reference:
+
+API reference
+=============
+
+.. currentmodule:: upref
+
+The objects on this page form the supported Upref v2 API. Start with
+:class:`ConfigStore` for persistence and use :func:`collect` only when the
+application needs interactive input.
+
+Public API summary
+------------------
+
+.. autosummary::
+
+   ConfigStore
+   Field
+   Prompter
+   collect
+   parse_bool
+   UprefError
+   ConfigPathError
+   ConfigFormatError
+   ConfigReadError
+   ConfigWriteError
+   MigrationError
+   PromptCancelled
+   PromptUnavailableError
+
+Configuration storage
+---------------------
+
+.. autoclass:: ConfigStore
+   :members:
+   :special-members: __init__
+
+Configuration types
+-------------------
+
+.. py:data:: Config
+
+   A configuration mapping with string keys and :data:`ConfigValue` values.
+
+.. py:data:: ConfigValue
+
+   A recursive type alias accepting ``None``, ``bool``, ``int``, ``float``,
+   ``str``, lists of supported values, and dictionaries with string keys.
+
+.. py:data:: prompt.PromptMode
+
+   The collection mode literal: ``"missing"`` or ``"all"``.
+
+Interactive schema and protocol
+-------------------------------
+
+.. autoclass:: Field
+   :members:
+
+.. autoclass:: Prompter
+   :members:
+
+.. autofunction:: collect
+
+.. autofunction:: parse_bool
+
+Built-in interfaces
+-------------------
+
+.. autoclass:: upref.tty.TTYPrompter
+   :members:
+   :special-members: __init__
+
+.. autoclass:: upref.gui.GuiPrompter
+   :members:
+   :special-members: __init__, __enter__, __exit__
+
+Exceptions
+----------
+
+.. autoexception:: UprefError
+   :show-inheritance:
+
+.. autoexception:: ConfigPathError
+   :show-inheritance:
+
+.. autoexception:: ConfigFormatError
+   :show-inheritance:
+
+.. autoexception:: ConfigReadError
+   :show-inheritance:
+
+.. autoexception:: ConfigWriteError
+   :show-inheritance:
+
+.. autoexception:: MigrationError
+   :show-inheritance:
+
+.. autoexception:: PromptCancelled
+   :show-inheritance:
+
+.. autoexception:: PromptUnavailableError
+   :show-inheritance:
+
+Package metadata
+----------------
+
+``upref.__version__`` contains the installed distribution version.
+``upref.__author__``, ``upref.__license__``, and ``upref.__copyright__``
+describe the package's authorship and license.

upref-2.2.0/docs/changelog.md

@@ -0,0 +1,2 @@
+```{include} ../CHANGELOG.md
+```

upref-2.2.0/docs/concepts.rst

@@ -0,0 +1,109 @@
+.. _concepts:
+
+Configuration model
+===================
+
+Upref deliberately has a small data model and an explicit lifecycle. An
+application normally performs three independent steps:
+
+1. create a :class:`~upref.ConfigStore` and :meth:`~upref.ConfigStore.load`
+   values;
+2. optionally use :func:`~upref.collect` to ask for values;
+3. explicitly :meth:`~upref.ConfigStore.save` the final mapping.
+
+Loading never opens a terminal or window. Collecting never writes a file.
+This separation makes startup, cancellation, testing, and error recovery
+predictable.
+
+.. _config-values:
+
+Supported values
+----------------
+
+The document root is always a mapping with string keys. Each value can be one
+of the following:
+
+.. list-table::
+   :header-rows: 1
+   :widths: 28 72
+
+   * - Python value
+     - YAML representation
+   * - ``None``
+     - ``null``
+   * - ``bool``
+     - ``true`` or ``false``
+   * - ``int`` or ``float``
+     - A YAML number
+   * - ``str``
+     - A Unicode YAML string
+   * - ``list``
+     - A sequence whose items are supported values
+   * - ``dict[str, ConfigValue]``
+     - A nested mapping with string keys
+
+Empty strings, empty containers, ``False``, and ``0`` are valid values. An
+empty document or explicit YAML ``null`` at the root represents an empty
+mapping. A list or non-null scalar at the document root is invalid. Mapping
+keys at every level must be strings. Keys derived from ``str``, including
+string-backed enum members, are normalized to ordinary strings using their
+underlying text. A customized ``__str__`` display does not rename the key.
+If distinct custom keys normalize to the same text, validation rejects the
+collision instead of discarding a value.
+
+Values such as ``pathlib.Path``, ``datetime``, tuples, sets, enum
+members, and application classes are not converted implicitly. Convert them
+to a supported representation before calling
+:meth:`~upref.ConfigStore.save`.
+
+Cycles are rejected because YAML configuration must be a finite tree. Shared
+mutable objects are copied independently when accepted.
+
+Detached values and no cache
+----------------------------
+
+Upref validates and copies the complete value tree at its public boundaries.
+Inputs are never mutated, and returned dictionaries do not share nested lists
+or dictionaries with caller-owned defaults or changes.
+
+Every :meth:`~upref.ConfigStore.load` reads the file again; a store has no
+implicit configuration cache. Mutating a loaded dictionary therefore changes
+only that Python object until :meth:`~upref.ConfigStore.save` is called.
+
+.. _merge-semantics:
+
+Recursive merge rules
+---------------------
+
+Defaults and updates use the same merge rules:
+
+* nested mappings are merged recursively;
+* a value from the overriding mapping wins;
+* lists and scalars are replaced in full, not concatenated;
+* keys found only in the overriding mapping are retained;
+* both inputs and the result remain independent.
+
+For example, given these defaults and saved values:
+
+.. code-block:: python
+
+   defaults = {
+       "network": {"host": "localhost", "ports": [8000, 8001]},
+       "enabled": True,
+   }
+   saved = {
+       "network": {"ports": [9000]},
+       "enabled": False,
+   }
+
+the resolved configuration is:
+
+.. code-block:: python
+
+   {
+       "network": {"host": "localhost", "ports": [9000]},
+       "enabled": False,
+   }
+
+See :doc:`storage` for the difference between in-memory defaults and persisted
+updates.

upref-2.2.0/docs/conf.py

@@ -0,0 +1,52 @@
+"""Sphinx configuration for the Upref documentation."""
+
+from __future__ import annotations
+
+import sys
+from pathlib import Path
+
+PROJECT_ROOT = Path(__file__).resolve().parents[1]
+sys.path.insert(0, str(PROJECT_ROOT))
+
+import upref  # noqa: E402  (the source tree must be importable first)
+
+# Project information
+project = "upref"
+author = upref.__author__
+copyright = f"2026, {author}"
+release = upref.__version__
+version = ".".join(release.split(".")[:2])
+
+# General configuration
+extensions = [
+    "sphinx.ext.autodoc",
+    "sphinx.ext.autosummary",
+    "sphinx.ext.napoleon",
+    "myst_parser",
+]
+
+autosummary_generate = True
+autodoc_member_order = "bysource"
+autodoc_typehints = "description"
+nitpicky = True
+nitpick_ignore_regex = [
+    ("py:class", r"(collections\.abc\.)?(Callable|Mapping)"),
+    ("py:class", r"(os\.)?PathLike"),
+    ("py:class", r"pathlib\.Path"),
+    ("py:class", r"(PrintFunction|ReadFunction)"),
+    ("py:func", r"(getpass\.getpass|input|print)"),
+    ("py:mod", r"platformdirs"),
+]
+
+source_suffix = {
+    ".rst": "restructuredtext",
+    ".md": "markdown",
+}
+root_doc = "index"
+language = "en"
+exclude_patterns = ["_build", "Thumbs.db", ".DS_Store"]
+
+# HTML output
+html_theme = "sphinx_rtd_theme"
+html_static_path = ["layout"]
+html_css_files = ["extra.css"]