nti.site offers a set of classes and utility functions to integrate non-persistent name-based configuration of components using z3c.baseregistry with persistent in-database components. These are mixed and matched at runtime as needed to keep one “main” application persistent site in the component lookup order.
For complete details and the changelog, see the documentation.
Release files for nti.site 3.2.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 | Actions |
|---|---|---|---|---|
| nti_site-3.2.0.tar.gz | 55.7 kB | Without provenance | Details for nti_site-3.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| nti_site-3.2.0-py3-none-any.whl | Python 3 | none | any | Details for nti_site-3.2.0-py3-none-any.whl |
Total release size: 106.5 kB
Release files / nti_site-3.2.0.tar.gz
| Download URL | nti_site-3.2.0.tar.gz |
|---|---|
| Size | 55.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7504889c602b034d68c0009914adfedf1c208b71f7b4c977c36d01d039778431
|
|
BLAKE2b-256 checksum How to use checksums |
b2cfb65255b8a79c07662b671a30c216e95de38b83c12312981026e79d943f22
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.14
|
Release files / nti_site-3.2.0-py3-none-any.whl
| Download URL | nti_site-3.2.0-py3-none-any.whl |
|---|---|
| Size | 50.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4bb8c04f3b38b6892a7e222668a22c282b5b605eb96614e56847ea380c51192d
|
|
BLAKE2b-256 checksum How to use checksums |
3fe6f8e40800644ebe763b394709f60695ba1852ed18c8dd266abc9c05d73466
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.14
|
Security for nti.site 3.2.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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
