Code generation based on specifications.
Neverfails involves an ambitious idea: code generation based on specifications. This idea does not depend on a specific platform or programming language. In principle, it could be implemented with any framework. Actually, I have decided to test it using Django as a web framework and Python as the programming language.
Similarly to lettuce, neverfails recognizes the steps using regular expressions and checks whether they pass or fail. If the step fails, neverfails does not raise an AssertionError but runs the code to make the step pass, then runs the step again.
1 maintainer
Metadata
1 maintainer
Release files for neverfails 0.0.1
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 |
|---|---|---|---|---|
| neverfails-0.0.1.tar.gz | 6.6 kB | Without provenance | Details for neverfails-0.0.1.tar.gz |
Release files / neverfails-0.0.1.tar.gz
| Download URL | neverfails-0.0.1.tar.gz |
|---|---|
| Size | 6.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6ad18458d639fe29be4ade2307dad0cd61742815d4dd5d3d99d126ba8434e915
|
|
BLAKE2b-256 checksum How to use checksums |
6df9f6c17556caf861d94215094013c28d0621c455c1bcc1241803cafd2a818d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for neverfails 0.0.1
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.
