Machinery
This is a collection of functionality.
Docs found at https://machinery.readthedocs.io
History
Between June 2016 and July 2021 I (@delfick) worked at LIFX and created the private version of https://photons.delfick.com (with the open source version coming out in March 2018.
In this project I created a bunch of utilities, especially around using asyncio code without creating memory leaks or annoying warnings when tasks aren’t awaited before the end of the program.
In November 2023 I started this project to extract those helpers so they can be used independently of Photons and so I could make them strongly typed and tested better.
In April 2025, the initial wave of those helpers were rewritten to be strongly typed with a slightly different approach to a number of those concepts.
1 maintainer
Metadata
1 maintainer
Release files for machinery-collection 0.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 |
|---|---|---|---|---|
| machinery_collection-0.3.1.tar.gz | 29.3 kB | With provenance | Details for machinery_collection-0.3.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| machinery_collection-0.3.1-py3-none-any.whl | Python 3 | none | any | Details for machinery_collection-0.3.1-py3-none-any.whl |
Total release size: 67.4 kB
Release files / machinery_collection-0.3.1.tar.gz
| Download URL | machinery_collection-0.3.1.tar.gz |
|---|---|
| Size | 29.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
26436ecbd322208f5a451aa6f0514dbfc5de1279002b15c5656540489376a479
|
|
BLAKE2b-256 checksum How to use checksums |
bb467b24095beffcd4dd67ad99c4a587b887dce8a966409da96812b76014215e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 18, 2026.
Transparency logRelease files / machinery_collection-0.3.1-py3-none-any.whl
| Download URL | machinery_collection-0.3.1-py3-none-any.whl |
|---|---|
| Size | 38.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c0aedd42b86a81a4d9ce40aed89be197312e03ef942053356b9b7184fcba9100
|
|
BLAKE2b-256 checksum How to use checksums |
d3baacf06bafb0254e60db84d7c15216089b3d4805a404b5420f0ea2a473c7e0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 18, 2026.
Transparency logSecurity for machinery-collection 0.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for machinery_collection-0.3.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 May 18, 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.
