Skip to main content

Maison

Actions Status Actions Status codecov PyPI version

Read configuration settings from configuration files.

📚 View Documentation | 🐛 Report a Bug | ✨ Request a Feature


Motivation

When developing a python package, e.g a command-line tool, it can be helpful to allow the user to set their own configuration options to allow them to tailor the tool to their needs. These options are typically set in files in the root of a user's directory that uses the tool, for example in a pyproject.toml or an {project_name}.ini file.

maison aims to provide a simple and flexible way to read and validate those configuration options so that they may be used in the package.

Features

  • Supports multiple config files and multiple config filetypes.
  • Optional merging of multiple configs.
  • Optional config validation with pydantic.
  • Caching of config files for quick access.
  • Fully tested and typed.

Installation

You can install maison via pip from PyPI:

pip install maison

Installation for Development

To set up maison for local development:

  1. Clone the repository:
    git clone https://github.com/dbatten/maison.git
    cd maison
    
  2. Install dependencies using :term:uv:
    uv sync
    
  3. Install pre-commit hooks:
    uvx nox -s pre-commit -- install
    

This sets up a virtual environment and installs core, development, and quality check dependencies.

Usage

Suppose the following pyproject.toml lives somewhere in a user's directory:

[tool.acme]
enable_useful_option = true

maison exposes a UserConfig class to retrieve values from config files like so:

from maison import UserConfig

from my_useful_package import run_useful_action

config = UserConfig(package_name="acme")

if config.values["enable_useful_option"]:
    run_useful_action()

Development Workflow

This project uses a robust set of tools for development, testing, and quality assurance. All significant automated tasks are run via :term:Nox, orchestrated by the central noxfile.py.

  • Run all checks (lint, typecheck, security): uvx nox -s check
  • Run test suite with coverage: uvx nox -s test
  • Build documentation: uvx nox -s docs
  • Build package: uvx nox -s build
  • See all available tasks: uvx nox -l

Explore the noxfile.py and the project documentation for detailed information on the automated workflow.

Contributing

(This section should guide contributions to this specific generated project, not the template. It should refer to the project's CODE_OF_CONDUCT.md and link to a CONTRIBUTING.md specific to the project, if you choose to generate one.)

Report bugs or suggest features via the issue tracker.

See CONTRIBUTING.md for contribution guidelines.

License

Distributed under the terms of the MIT license. See LICENSE for details.


This project was generated from the cookiecutter-robust-python template.

Metadata

Release files for maison 2.0.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for maison 2.0.2
File Size Uploaded
maison-2.0.2.tar.gz 16.0 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for maison 2.0.2
File Interpreter ABI Platform
maison-2.0.2-py3-none-any.whl Python 3 none any Details

Total release size: 29.5 kB

Release files / maison-2.0.2.tar.gz

Download URL maison-2.0.2.tar.gz
Size 16.0 kB
Tags Source
SHA-256 checksum
How to use checksums
476f2bf414a20f5abf5a9856bd4db78b5a33c695654a0fc49c3c4abed78c2efc
BLAKE2b-256 checksum
How to use checksums
24457cb1d08b6b5674c381b6e0232d35f417a1eba8bb66cdc18edff2b9c80b68
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 9, 2025.

Transparency log

Release files / maison-2.0.2-py3-none-any.whl

Download URL maison-2.0.2-py3-none-any.whl
Size 13.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
835de804aa8063795b48c4fe2b4918106cfda4e5df515e8784ec9fa64cd28191
BLAKE2b-256 checksum
How to use checksums
5b8f3f0895a18cad5afd61c16ac38d35a2466f0cac8ae5c28f1a67f7a81bcdec
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 9, 2025.

Transparency log

Release history Release notifications | RSS feed

This release

2.0.2 This release

2 release files

2.0.1

2 release files

2.0.0

2 release files

1.4.3

2 release files

1.4.2

2 release files

1.4.1

2 release files

1.4.0

2 release files

1.3.0

2 release files

1.2.3

2 release files

1.2.2

2 release files

1.2.1

2 release files

1.2.0

2 release files

1.1.0

2 release files

1.0.0

2 release files

0.1.0

2 release files

0.0.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page