Skip to main content

confiq

confiq


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


Installation

You can install confiq via pip from PyPI:

pip install confiq

Installation for Development

To set up confiq for local development:

  1. Clone the repository:
    git clone https://github.com/56kyle/confiq.git
    cd confiq
    
  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

(This section should explain how to use the generated application. Replace the content below with instructions specific to your project's functionality. If your project is a library, show import examples. If it's a CLI application, show command examples. Link to the full documentation for details.)

As a Library

# Example usage of your package as a library
# from confiq import some_function
# result = some_function()
# print(result)

As a Command-Line Application

If your project defines command-line entry points in pyproject.toml:

# Example usage of your CLI application
# confiq --help
# confiq do-something --input file.txt

For detailed API documentation and CLI command references, see the Documentation.

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 confiq 0.1.0

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

Source distribution (sdist)

Source distribution for confiq 0.1.0
File Size Uploaded
confiq-0.1.0.tar.gz 4.0 kB Details

Built distribution (wheel)

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

Total release size: 8.0 kB

Release files / confiq-0.1.0.tar.gz

Download URL confiq-0.1.0.tar.gz
Size 4.0 kB
Tags Source
SHA-256 checksum
How to use checksums
858824814d8b9bda3339c6fe0fcfa0633e275d443b12f9e19569a1357a8cd692
BLAKE2b-256 checksum
How to use checksums
ba87db5bc2b0a8b782b203a64f11fd6b3c5c8b92a46e22b7f17aea3ae5e9c075
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

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 May 25, 2026.

Transparency log

Release files / confiq-0.1.0-py3-none-any.whl

Download URL confiq-0.1.0-py3-none-any.whl
Size 4.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
d1283b011807da5fe2ff28e2bafec6ab38d85919df8b8c1ce536ec43dc4c67b5
BLAKE2b-256 checksum
How to use checksums
9468fcf7467169af5281061e3ed7e0c235a59e182a4ee9f7c3b38d652d097457
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

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 May 25, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.0 This release

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