pyorderly
Table of Contents
Installation
pip install pyorderly
Development
Useful hatch commands:
hatch shell
hatch run test
hatch run cov
hatch run lint:style
hatch run lint:fmt
Modifying the parser
The outpack query parser is implemented in Rust as part of the
outpack_server repository. When
developing new features in the query parser, they can be tested out in your
development environment of pyorderly by installing the parser from your local
checkout:
hatch run pip install /path/to/outpack_server
Releasing
- Increment the version number using the
hatch versioncommand. - Commit the changes and create a PR.
- Get the PR approved and merged to main.
- Create a GitHub release:
- Set the tag name as
vX.Y.Z, matching the version reported by hatch. - Write some release notes (possibly using the
Generate release notesbutton). - Publish the release!
- Set the tag name as
- Sit back and relax while the release gets built and published.
- Check that the new version is available on PyPI.
License
pyorderly is distributed under the terms of the MIT license.
2 maintainers
Metadata
2 maintainers
Release files for pyorderly 0.2.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 | |
|---|---|---|---|---|
| pyorderly-0.2.1.tar.gz | 74.6 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pyorderly-0.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 123.9 kB
Release files / pyorderly-0.2.1.tar.gz
| Download URL | pyorderly-0.2.1.tar.gz |
|---|---|
| Size | 74.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9aab416207bcd9e4530ce1aed0cfdc8eb6e695ec70b023c5c5acb86bc898cd45
|
|
BLAKE2b-256 checksum How to use checksums |
1b633b525d16a120acfe46774ea4f843bb49871d96b7bb12a05df8a0ce0e68e6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Jan 15, 2026.
Transparency logRelease files / pyorderly-0.2.1-py3-none-any.whl
| Download URL | pyorderly-0.2.1-py3-none-any.whl |
|---|---|
| Size | 49.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
68a682285edbf708c0479a419bfeca8f3dffcc1e51bd57ff663b13937a0f47b8
|
|
BLAKE2b-256 checksum How to use checksums |
60f1a689a050a45eb2ca1663ca4f5992f130e20c8a7964d11d0d90d178bebaa7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Jan 15, 2026.
Transparency logSecurity for pyorderly 0.2.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for pyorderly-0.2.1.tar.gz
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 Jan 15, 2026.
Transparency logA 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.
