ProofCheck: Checking Mathematical Proofs Written in TeX
Mathematical proofs are sequences of steps which take expressions in a formal language which state something already known to another formal expression which becomes known as a result. Each step must be justified by a rule of inference. The notion of proof is sharpened when the set of inference rules is reduced to a small number. But the effect of such reduction on proofs is to make them cumbersome, like the computations of a Turing Machine. ProofCheck uses a really large rule set to make possible proofs which are not cumbersome. The default inference rule set currently contains over 1500 rules and is still growing.
Either TeX or LaTeX may be used. What is required in the way of document structure is that:
1. Each theorem must be labeled and numbered in number-dot-number style,
2. Each theorem and proof must be expressed in a language that ProofCheck can learn to parse, and
3. Proof steps must be numbered and annotated following ProofCheck syntax.
The work cycle is as follows:
Edit the document using your preferred text editor:
emacs article.tex
TeX the document:
tex article
Parse the document:
parse.py article
Check a proof of, say theorem 1.23:
check.py article 1.23
Errors at any stage of course send you back to the text editor.
Metadata
Release files for proofcheck 1.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 |
|---|---|---|---|---|
| proofcheck-1.0.tar.gz | 149.5 kB | Without provenance | Details for proofcheck-1.0.tar.gz |
Release files / proofcheck-1.0.tar.gz
| Download URL | proofcheck-1.0.tar.gz |
|---|---|
| Size | 149.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
de050ce172c04d99473e06af72267d1e26e6b109484c179b97943879c4c585fe
|
|
BLAKE2b-256 checksum How to use checksums |
800acb9b75995104af93ce7b151f0e134ca476359a8b5001319649a866d9dea3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for proofcheck 1.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.