cantorpairs
(Almost) Cantor pairing and extension to tupling
Ancillary project for the related initiative PReFScript.
See https://github.com/balqui/prefscript
for further information.
Project started: mid Germinal 2003.
Current version: probably 1.3.1, early Brumaire 2026,
Implements (a slight variant of) the Cantor pairing function and its projections. See the example at the end of this file for a quick review.
Provides as well an Exception-based variant of "assert" that is not disabled from the command line: call ensure.that(assertion, "message") to resort to it.
No previous version was ever pip-installable; instead,
these programs were handled as a Git submodule of the
prefscript repo and one would download the source or
clone the repo when in need of using it standalone.
However, this structure led to considerable headaches
in making installable a fully correct version of
prefscript and for the coming versions the decision
was to employ cantorpairs as a standard dependency,
which requires upload to PyPI: this is the version
that has that goal. A number of ideas (see Issues)
also suggest that this module might grow in the near
future, along its way to fulfill Greenspun's tenth rule.
Follows relatively closely
https://en.wikipedia.org/wiki/Pairing_function
with a slight difference: Pairs will work like dotted pairs
in creating tuples, hence a nil notion is necessary
(cf.
https://en.wikipedia.org/wiki/Cons).
To this end, the natural number zero is used as nil and the
dotted pair is a bijection between N x N and N - {0}.
The formulas have been adapted slightly to obtain this bijection.
Functions are defined in file cantorpairs_src.py whereas file
cp_ex.py contains the examples given below. The __init__ file
in the upper folder allows one to import functions from outside.
Compare cp_ex.py and cp_ex_alt.py to see how to import the
exposed functions in each case. This repo contains also right now
an Ensure class left undocumented on purpose.
Pairing examples
(Dotted) Pair formation (a.k.a. cons to Lispers) is dp(x, y).
The inverses are the left and right projections pr_L (for Left)
and pr_R (for Right), extended to map to zero for input zero.
Thus, dp(pr_L(x), pr_R(x)) == x if x != 0.
Early versions of these sources used pr_l (an ell, for left)
which was easily confused with number 1. Currently both projections
are marked with upper case L and (accordingly) R.
According to
https://import-as.github.io,
it is infrequent that
packages are imported as cp; the ones that do are cvxpy, copy,
cupy and chaospy: there is no consensus and most of these packages
are unlikely to be used in the same project as cantorpairs. Hence,
the user project prefscript runs a command import cantorpairs as cp
and I suggest to maintain that shorthand when possible, while importing
as cpt (for "Cantor pairs and tuples") only in case of conflict.
import cantorpairs as cp
for i in range(4):
for j in range(4):
print(i, j, cp.dp(i, j))
for i in range(90, 100):
print(cp.pr_L(i), cp.pr_R(i), cp.dp(cp.pr_L(i), cp.pr_R(i)), i)
Tupling exemples
In order to have unbounded-length tuples, a tuple is either empty (mapped to zero as "nil") or a pair formed by the first element and the rest of the tuple. All this is very traditional in some cultures.
There are two functions that form tuples: in one, tup_e,
the arguments are explicitly integers, an arbitrary number
of them. In the other, tup_i, the single argument is an
iterable of integers. We can extract values from tuples
(besides using pr_L and pr_R) with the suffix tuple function
s_tup(t, k) that discards the first k components and returns
the tuple starting at position k (counting from zero) and the
general projection function pr(t, k) that retrieves the component
at position k (again counting from zero). If k is too large,
pr(t, k) returns zero (and it is not a bug but a feature).
Conversely, seq(z) iterates enough so as to unpack the sequence
encoded by z and return it in the form of a Python list.
t = cp.tup_e(4, 7, 56, 101)
for i in range(5):
'last call is actually out of range'
print(cp.pr(t, i))
st = cp.s_tup(t, 2)
print(st)
for i in range(3):
print(cp.pr(st, i))
print(cp.seq(54321)
print(t, cp.seq(t))
while t:
print(t, cp.pr_L(t))
t = cp.pr_R(t)
t = cp.tup_i(range(8, 16))
while t:
print(t, cp.pr_L(t))
t = cp.pr_R(t)
Metadata
Release files for cantorpairs 1.3.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 |
|---|---|---|---|---|
| cantorpairs-1.3.1.tar.gz | 5.8 kB | Without provenance | Details for cantorpairs-1.3.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cantorpairs-1.3.1-py3-none-any.whl | Python 3 | none | any | Details for cantorpairs-1.3.1-py3-none-any.whl |
Total release size: 12.6 kB
Release files / cantorpairs-1.3.1.tar.gz
| Download URL | cantorpairs-1.3.1.tar.gz |
|---|---|
| Size | 5.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d2f3539f7d9a7967d3705345fa7d0b635f08b5808d7dd01e8db1f231b83c0fb0
|
|
BLAKE2b-256 checksum How to use checksums |
b92ce174ec958dc6295baf92336f04f4cc2ea2d3b3923c7baf771bcf940c0932
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / cantorpairs-1.3.1-py3-none-any.whl
| Download URL | cantorpairs-1.3.1-py3-none-any.whl |
|---|---|
| Size | 6.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c2b85a3883bead5b39a645543032bbc1b452830c7723d98610caa51804aa6777
|
|
BLAKE2b-256 checksum How to use checksums |
2c7f583a3504725e4ca31eb4bec4638bf9b2bf2e41222273706d9b8b28130b71
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for cantorpairs 1.3.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.