Naylence factory
Naylence factory is the resource factory and extension management framework for the Naylence ecosystem. It provides a structured way to define, register, and instantiate resources (connectors, stores, clients, etc.) using Pydantic-based configuration, priority-based defaults, and plugin-style extension loading.
Features
- 🏭 Resource Factories — Define factories that build typed resources from configs.
- 🔌 Extension Management — Discover and register implementations via Python entry points.
- ⚡ Priority-based Defaults — Automatically select the “best” default implementation.
- 🧩 Composable Configs — Pydantic models with expression support (
${env:VAR:default}). - 🔒 Policy-driven Evaluation — Control how config expressions are handled: evaluate, literal, or error.
- 🔄 Polymorphic Dispatch — Automatically instantiate subclasses based on
typefields.
Installation
pip install naylence-factory
Requires Python 3.12+.
License
Apache 2.0 © Naylence Dev
1 maintainer
Metadata
1 maintainer
Release files for naylence-factory 0.1.7
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 | |
|---|---|---|---|---|
| naylence_factory-0.1.7.tar.gz | 17.5 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| naylence_factory-0.1.7-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 38.7 kB
Release files / naylence_factory-0.1.7.tar.gz
| Download URL | naylence_factory-0.1.7.tar.gz |
|---|---|
| Size | 17.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a28f36e5c66a72337e06ba68d760d96ba4b8cb71e1cddd22888b9c17ed5fb010
|
|
BLAKE2b-256 checksum How to use checksums |
5a79f81843d70da518340ec1e3bbf3748bd58951c03bb15842affa06d9c3de27
|
| 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 Apr 18, 2026.
Transparency logRelease files / naylence_factory-0.1.7-py3-none-any.whl
| Download URL | naylence_factory-0.1.7-py3-none-any.whl |
|---|---|
| Size | 21.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dd8468587adbfc6f689c9d4d621a31388fd1b2ab729b305559d39bc0b67bb1da
|
|
BLAKE2b-256 checksum How to use checksums |
4c6c76278c54d94952396bd485ad8b8c9c2e8f59df1dcc4e275a37a275c97353
|
| 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 Apr 18, 2026.
Transparency logSecurity for naylence-factory 0.1.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for naylence_factory-0.1.7.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 Apr 18, 2026.
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
