Parsing Expressions
pe is a library for parsing expressions, including parsing expression grammars (PEGs). It aims to join the expressive power of parsing expressions with the familiarity of regular expressions. For example:
>>> import pe
>>> pe.match(r'"-"? [0-9]+', '-38') # match an integer
<Match object; span=(0, 3), match='-38'>
A grammar can be used for more complicated or recursive patterns:
>>> float_parser = pe.compile(r'''
... Start <- INTEGER FRACTION? EXPONENT?
... INTEGER <- "-"? ("0" / [1-9] [0-9]*)
... FRACTION <- "." [0-9]+
... EXPONENT <- [Ee] [-+]? [0-9]+
... ''')
>>> float_parser.match('6.02e23')
<Match object; span=(0, 7), match='6.02e23'>
Quick Links
Features and Goals
- Grammar notation is backward-compatible with standard PEG with few extensions
- A specification describes the semantic effect of parsing (e.g., for mapping expressions to function calls)
- Parsers are often faster than other parsing libraries, sometimes by a lot; see the benchmarks
- The API is intuitive and familiar; it's modeled on the standard API's re module
- Grammar definitions and parser implementations are separate
- Optimizations target the abstract grammar definitions
- Multiple parsers are available (currently packrat for recursive descent and machine for an iterative "parsing machine" as from Medeiros and Ierusalimschy, 2008 and implemented in LPeg).
Syntax Overview
pe is backward compatible with standard PEG syntax and it is conservative with extensions.
# terminals
. # any single character
"abc" # string literal
'abc' # string literal
[abc] # character class
# repeating expressions
e # exactly one
e? # zero or one (optional)
e* # zero or more
e+ # one or more
e{5} # exactly 5
e{3,5} # three to five
# combining expressions
e1 e2 # sequence of e1 and e2
e1 / e2 # ordered choice of e1 and e2
(e) # subexpression
# lookahead
&e # positive lookahead
!e # negative lookahead
# (extension) capture substring
~e # result of e is matched substring
# (extension) binding
name:e # bind result of e to 'name'
# grammars
Name <- ... # define a rule named 'Name'
... <- Name # refer to rule named 'Name'
# (extension) auto-ignore
X < e1 e2 # define a rule 'X' with auto-ignore
Matching Inputs with Parsing Expressions
When a parsing expression matches an input, it returns a Match
object, which is similar to those of Python's
re module for regular
expressions. By default, nothing is captured, but the capture operator
(~) emits the substring of the matching expression, similar to
regular expression's capturing groups:
>>> e = pe.compile(r'[0-9] [.] [0-9]')
>>> m = e.match('1.4')
>>> m.group()
'1.4'
>>> m.groups()
()
>>> e = pe.compile(r'~([0-9] [.] [0-9])')
>>> m = e.match('1.4')
>>> m.group()
'1.4'
>>> m.groups()
('1.4',)
Value Bindings
A value binding extracts the emitted values of a match and associates
it with a name that is made available in the Match.groupdict()
dictionary. This is similar to named-capture groups in regular
expressions, except that it extracts the emitted values and not the
substring of the bound expression.
>>> e = pe.compile(r'~[0-9] x:(~[.]) ~[0-9]')
>>> m = e.match('1.4')
>>> m.groups()
('1', '4')
>>> m.groupdict()
{'x': '.'}
Actions
Actions (also called "semantic actions") are callables that transform parse results. When an arbitrary function is given, it is called as follows:
func(*match.groups(), **match.groupdict())
The result of this function call becomes the only emitted value going forward and all bound values are cleared.
For more control, pe provides the Action class and a number of subclasses for various use-cases. These actions have access to more information about a parse result and more control over the match. For example, the Pack class takes a function and calls it with the emitted values packed into a list:
func(match.groups())
And the Join class joins all emitted strings with a separator:
func(sep.join(match.groups()), **match.groupdict())
Auto-ignore
The grammar can be defined such that some rules ignore occurrences of a pattern between sequence items. Most commonly, this is used to ignore whitespace, so the default ignore pattern is simple whitespace.
>>> pe.match("X <- 'a' 'b'", "a b") # regular rule does not match
>>> pe.match("X < 'a' 'b'", "a b") # auto-ignore rule matches
<Match object; span=(0, 3), match='a b'>
This feature can help to make grammars more readable.
Example
Here is one way to parse a list of comma-separated integers:
>>> from pe.actions import Pack
>>> p = pe.compile(
... r'''
... Start <- "[" Values? "]"
... Values <- Int ("," Int)*
... Int < ~( "-"? ("0" / [1-9] [0-9]*) )
... ''',
... actions={'Values': Pack(list), 'Int': int})
>>> m = p.match('[5, 10, -15]')
>>> m.value()
[5, 10, -15]
Similar Projects
1 maintainer
Metadata
1 maintainer
Release files for pe 0.6.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 | |
|---|---|---|---|
| pe-0.6.0.tar.gz | 210.1 kB | Details |
Built distributions (wheels)
Total release size: 13.8 MB
Release files / pe-0.6.0.tar.gz
| Download URL | pe-0.6.0.tar.gz |
|---|---|
| Size | 210.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dabec4ba7bd5fe2ab11a39a4343feaa453f002082918586a64b9216d550787e6
|
|
BLAKE2b-256 checksum How to use checksums |
2975db4b5e5e11abc751b4b0c4c0a47d26265bda403f771c5d189f8129607d0d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 18, 2025.
Transparency logRelease files / pe-0.6.0-cp313-cp313-win_amd64.whl
| Download URL | pe-0.6.0-cp313-cp313-win_amd64.whl |
|---|---|
| Size | 307.0 kB |
| Tags | CPython 3.13 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
cc2ab8a9399f177de4fb02d20c42b7c993a2bd14d9db310d16e331112a449974
|
|
BLAKE2b-256 checksum How to use checksums |
cd8a2ec1d45c440c990de38efdfadb160318cee1d2e09f5efc22d116a085686d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 18, 2025.
Transparency logRelease files / pe-0.6.0-cp313-cp313-musllinux_1_2_x86_64.whl
| Download URL | pe-0.6.0-cp313-cp313-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 1.0 MB |
| Tags | CPython 3.13 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
1c78e9c9a7a198b03e3142e37eeab2d032c64ff38d5fa028028b1dda2afb8f18
|
|
BLAKE2b-256 checksum How to use checksums |
b9c6ca68d5a9ab8542103c857315cc00895e5b4c7033b09f3dc2a582df156dcc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 18, 2025.
Transparency logRelease files / pe-0.6.0-cp313-cp313-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl
| Download URL | pe-0.6.0-cp313-cp313-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl |
|---|---|
| Size | 1.1 MB |
| Tags | CPython 3.13 Linux glibc 2.28+ x86-64 Linux glibc 2.5+ x86-64 |
|
SHA-256 checksum How to use checksums |
0da30d1567ee4fc77e2c30061f089e73226f926246e4368e6442e6802aeb0f77
|
|
BLAKE2b-256 checksum How to use checksums |
90cb36365e2dc2b238762dccb4ed3eb659e002395f890a0732c99b593239ce01
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 18, 2025.
Transparency logRelease files / pe-0.6.0-cp313-cp313-macosx_11_0_arm64.whl
| Download URL | pe-0.6.0-cp313-cp313-macosx_11_0_arm64.whl |
|---|---|
| Size | 312.4 kB |
| Tags | CPython 3.13 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
1896d9b7f1fc6bb841c7ceb6744a43a43b158c07eeb486671b3f7bd07af6e9e5
|
|
BLAKE2b-256 checksum How to use checksums |
f4ef04d5cecf16528592422e176257bd4c040010312c2e72f1a7ecc48af76ba5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 18, 2025.
Transparency logRelease files / pe-0.6.0-cp312-cp312-win_amd64.whl
| Download URL | pe-0.6.0-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 306.7 kB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
1138d94cc3eacd194351ddf6575c3070352c868f38e59407c98434af599ba130
|
|
BLAKE2b-256 checksum How to use checksums |
edd4f683509515a00e266ef4922a360eeb8e3e24dfdcb6dc18c24a69d1e4e7b3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 18, 2025.
Transparency logRelease files / pe-0.6.0-cp312-cp312-musllinux_1_2_x86_64.whl
| Download URL | pe-0.6.0-cp312-cp312-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 1.0 MB |
| Tags | CPython 3.12 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
e0613ed07964c6da0a0d18155009fb3b7cd189568ec228be47dda46fb5aa7e61
|
|
BLAKE2b-256 checksum How to use checksums |
cc4561a806fa55f0ec5e1f54d224db54c1e781eb0985faddd40f9d151434cba5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 18, 2025.
Transparency logRelease files / pe-0.6.0-cp312-cp312-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl
| Download URL | pe-0.6.0-cp312-cp312-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl |
|---|---|
| Size | 1.1 MB |
| Tags | CPython 3.12 Linux glibc 2.28+ x86-64 Linux glibc 2.5+ x86-64 |
|
SHA-256 checksum How to use checksums |
cc7e284c8214d96becc17bf77b3230a55d67399cbc89551443962665754968e8
|
|
BLAKE2b-256 checksum How to use checksums |
870e96571224d24468b480faf753f8f2a5f0812fdaab8b3f6ba866a9d8839133
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 18, 2025.
Transparency logRelease files / pe-0.6.0-cp312-cp312-macosx_11_0_arm64.whl
| Download URL | pe-0.6.0-cp312-cp312-macosx_11_0_arm64.whl |
|---|---|
| Size | 314.0 kB |
| Tags | CPython 3.12 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
85774b7a67302e8599dc10e68d68dc383a3817512c1acfa0d13656252d68a0b5
|
|
BLAKE2b-256 checksum How to use checksums |
98de33ac90ae4a0e6b8b4ff1f8ee4dc695cfc8df03996373e5ed73a9cc5491c1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 18, 2025.
Transparency logRelease files / pe-0.6.0-cp311-cp311-win_amd64.whl
| Download URL | pe-0.6.0-cp311-cp311-win_amd64.whl |
|---|---|
| Size | 310.6 kB |
| Tags | CPython 3.11 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
e005ccf5421d79c991f871f58e53ba32a0fb7a82db1a0c594ebb9e629a874775
|
|
BLAKE2b-256 checksum How to use checksums |
1328be8fd4b6a42e32771cb78ac272ed2f4e15c15c5a450e3ec0282076c4d0e5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 18, 2025.
Transparency logRelease files / pe-0.6.0-cp311-cp311-musllinux_1_2_x86_64.whl
| Download URL | pe-0.6.0-cp311-cp311-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 1.1 MB |
| Tags | CPython 3.11 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
2e74d1d06e7d68d163ddb4576c401b1e6f4cb769bbba8f6146b340bc8bada99b
|
|
BLAKE2b-256 checksum How to use checksums |
c937c03b1c658b71c36d2bfe1d1016e2824ad55eb895ac16d1cec4aa59bc2c3d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 18, 2025.
Transparency logRelease files / pe-0.6.0-cp311-cp311-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl
| Download URL | pe-0.6.0-cp311-cp311-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl |
|---|---|
| Size | 1.1 MB |
| Tags | CPython 3.11 Linux glibc 2.28+ x86-64 Linux glibc 2.5+ x86-64 |
|
SHA-256 checksum How to use checksums |
daf9241470c1e24481e925bb7af920e6ab986400ea9bb34734b0be44dd648e0e
|
|
BLAKE2b-256 checksum How to use checksums |
77f3c515b5a6da0a67c74b46339cb2915e2412fcd6b38b11f4a780c784b03827
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 18, 2025.
Transparency logRelease files / pe-0.6.0-cp311-cp311-macosx_11_0_arm64.whl
| Download URL | pe-0.6.0-cp311-cp311-macosx_11_0_arm64.whl |
|---|---|
| Size | 319.0 kB |
| Tags | CPython 3.11 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
8f5386de8727408bcdc0e61d3350d9fe47c69fb222500d04e532c001b937e17a
|
|
BLAKE2b-256 checksum How to use checksums |
9846c983a4327904c965d6d7e5fa4e42f0188229f966e65d4b033bf3f0c5f329
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 18, 2025.
Transparency logRelease files / pe-0.6.0-cp310-cp310-win_amd64.whl
| Download URL | pe-0.6.0-cp310-cp310-win_amd64.whl |
|---|---|
| Size | 310.2 kB |
| Tags | CPython 3.10 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
28b841d0a3ec0a94231d3d326c28d6cbf0eb9b4c2e89d9433cba717f1ae649ff
|
|
BLAKE2b-256 checksum How to use checksums |
773c8ca149fd548a1ca3c6c0572ac4b7f8ba7af73527f53339c28c345fbaf63f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 18, 2025.
Transparency logRelease files / pe-0.6.0-cp310-cp310-musllinux_1_2_x86_64.whl
| Download URL | pe-0.6.0-cp310-cp310-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 1.0 MB |
| Tags | CPython 3.10 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
cccbc56c7a49bb52db26f49dc6abbb5c6431eda28ff8c11ca107db509f9970c3
|
|
BLAKE2b-256 checksum How to use checksums |
0b437b336a4563ea9cc2e0bf6cf653bb6eb63768aab2440e28a143f0b2574213
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 18, 2025.
Transparency logRelease files / pe-0.6.0-cp310-cp310-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl
| Download URL | pe-0.6.0-cp310-cp310-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl |
|---|---|
| Size | 1.0 MB |
| Tags | CPython 3.10 Linux glibc 2.28+ x86-64 Linux glibc 2.5+ x86-64 |
|
SHA-256 checksum How to use checksums |
1db5386bdf0d5b5d5a1f9561e331019ff88b8eb287aa7f58fee440bdcf12f6ae
|
|
BLAKE2b-256 checksum How to use checksums |
cc3ad42708f3dd279bf19b7b8573cff1bef4b9d6594fd5d3700008858950f450
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 18, 2025.
Transparency logRelease files / pe-0.6.0-cp310-cp310-macosx_11_0_arm64.whl
| Download URL | pe-0.6.0-cp310-cp310-macosx_11_0_arm64.whl |
|---|---|
| Size | 316.8 kB |
| Tags | CPython 3.10 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
36d2058cd38c0f90bb4d4e28d87b2942fd417e7ff6a2cf29ff5a52d5f26930e1
|
|
BLAKE2b-256 checksum How to use checksums |
36f6604dfe44f95925723af18e7a6bc19a5fd55800227a8941efd410ab225695
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 18, 2025.
Transparency logRelease files / pe-0.6.0-cp39-cp39-win_amd64.whl
| Download URL | pe-0.6.0-cp39-cp39-win_amd64.whl |
|---|---|
| Size | 310.5 kB |
| Tags | CPython 3.9 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
a4c5e967b917f6848787257960334d6679e4ec19a5ae9b703a46529900c4cab0
|
|
BLAKE2b-256 checksum How to use checksums |
ad531e14b3aa0122e8829d79d1418c122a516168306642be6c50a3eabbbe9914
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 18, 2025.
Transparency logRelease files / pe-0.6.0-cp39-cp39-musllinux_1_2_x86_64.whl
| Download URL | pe-0.6.0-cp39-cp39-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 1.0 MB |
| Tags | CPython 3.9 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
1d410651b233fb369f38a881d8bf1d81a53d2614f31a6239b41b2c44e09b81cd
|
|
BLAKE2b-256 checksum How to use checksums |
3ffcfea3f78fdd88fad65d1aa192d40a718d591cba9f2d78ffa4e487351eb33e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 18, 2025.
Transparency logRelease files / pe-0.6.0-cp39-cp39-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl
| Download URL | pe-0.6.0-cp39-cp39-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl |
|---|---|
| Size | 1.0 MB |
| Tags | CPython 3.9 Linux glibc 2.28+ x86-64 Linux glibc 2.5+ x86-64 |
|
SHA-256 checksum How to use checksums |
39dc4520aeca336aaf12287a15a4799f61b45c44f78d6c05910f0bde6856fa78
|
|
BLAKE2b-256 checksum How to use checksums |
2ab12d756e6c0c67dfef0b5fb992a3e369fc137723f7c7de971a572eb1a85a8b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 18, 2025.
Transparency logRelease files / pe-0.6.0-cp39-cp39-macosx_11_0_arm64.whl
| Download URL | pe-0.6.0-cp39-cp39-macosx_11_0_arm64.whl |
|---|---|
| Size | 317.7 kB |
| Tags | CPython 3.9 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
0c5d4098644ced661b3ea8dcfea0db35cf48ed1242cb014cd4346de44d466a7f
|
|
BLAKE2b-256 checksum How to use checksums |
bb9c8568178256ca66afb7977287ec27ccefd3a1c70a1f55a741c2b563643f15
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 18, 2025.
Transparency log
