- Code-engine is a dead simple engine based on Jinja2 to make you free from generation process.
It looks like a pipe. You push your data into the end of the pipe. Finally, the files will be generated at the other end.
1 maintainer
Metadata
1 maintainer
Release files for code-engine 1.0.13
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 | |
|---|---|---|---|---|
| code_engine-1.0.13.tar.gz | 2.6 kB | Without provenance | Details |
Release files / code_engine-1.0.13.tar.gz
| Download URL | code_engine-1.0.13.tar.gz |
|---|---|
| Size | 2.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a592783984a880b89c30bcbe03c3557867d8f2a76a1a6dba367166d0b9a8ce5f
|
|
BLAKE2b-256 checksum How to use checksums |
8616ef61303da38a3aaa5549584cce2976cb7ed610e3e2f7a0635485b6895c88
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.20.1 setuptools/40.6.2 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/3.6.5
|
Security for code-engine 1.0.13
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.
