fillenv
Minimal Python project managed with uv.
Setup
# Create and sync environment (uses uv.lock/pyproject.toml)
uv sync
# Run a Python REPL using the environment
uv run python -V
Make commands
# Create and sync environment with dev/test extras
make setup
# Format code (ruff formatter)
make format
# Lint code (ruff lint)
make lint
# Run tests (pytest)
make test
Usage
Fill variables from a template and write KEY=value lines to a file:
# Install from PyPI
pip install fillenv
# Use the installed CLI (writes to .env or .env1, .env2, ...)
fillenv .env.template
# Or rely on default template path (".env.template" in CWD)
fillenv
# Alternatively via python -m
uv run python -m fillenv .env.template
# Or rely on default template path (".env.template" in CWD)
uv run python -m fillenv
# Specify output file (default: .env)
fillenv --output .env.production
# Overwrite existing output file
fillenv --overwrite
# Combine options
fillenv .env.template --output .env.local --overwrite
You can also import and call fillenv.cli.run(argv) from Python code.
Project layout
.
├── pyproject.toml
├── README.md
├── Makefile # common tasks: setup, format, lint, test
├── src/
│ └── fillenv/
│ ├── __init__.py
│ ├── __main__.py
│ ├── cli.py # entrypoint and command handling
│ ├── constants.py # shared constants
│ ├── parser.py # parse template into variables and prompts
│ ├── prompt.py # interactive prompting utilities
│ └── serialize.py # serialize variables to KEY=value lines
└── tests/...
Releasing
Update the version in pyproject.toml.
Create a build and upload to PyPI:
# Build (requires uv)
uv build
# Upload (requires twine and a configured token)
twine upload dist/*
Issues and releases:
- Issues: https://github.com/elmernocon/fillenv/issues
- Releases/Changelog: https://github.com/elmernocon/fillenv/releases
Metadata
Release files for fillenv 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| fillenv-1.0.0.tar.gz | 48.0 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| fillenv-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 55.3 kB
Release files / fillenv-1.0.0.tar.gz
| Download URL | fillenv-1.0.0.tar.gz |
|---|---|
| Size | 48.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c1e465e960140ac5a11aeb7ef327f05df2f2d93e154c3a1aade9309c614fbd4e
|
|
BLAKE2b-256 checksum How to use checksums |
99730539bc9d78b7f327eaf6383488179c92cbe1be85ac18e971fd87ab0102d4
|
| 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 Nov 2, 2025.
Transparency logRelease files / fillenv-1.0.0-py3-none-any.whl
| Download URL | fillenv-1.0.0-py3-none-any.whl |
|---|---|
| Size | 7.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e57cd7113e6c91afae9df531b73da7245de7c4c3ea5f22e4f2a1293472d54c16
|
|
BLAKE2b-256 checksum How to use checksums |
95e297aca7938c00520587b54e36af613ec8db80e6bf0fe07f7c9c16d987679c
|
| 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 Nov 2, 2025.
Transparency logSecurity for fillenv 1.0.0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for fillenv-1.0.0.tar.gz
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 Nov 2, 2025.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.