Introduction
Generic methods to use amqp
Changelog
0.13.1 (2026-03-16)
Fixed encoding error in error message. [chris-adam]
0.12 (2026-03-03)
Added function to add “finalized” state on eSigning sessions. [chris-adam]
0.11 (2025-12-16)
Removed to_sign and signed fields from the scanbehavior. [chris-adam]
Corrected collective.dms.scanbehavior.behaviors.IScanFields usage [sgeulette]
0.10 (2025-11-05)
Commented unneeded code. [sgeulette]
In utils.highest_scan_id, get scan_id from brain index instead metadata in case there is a desynchronization between index and metadata and we are sure we are re-using the same value as the one used to get the highest index value. [gbastien]
0.9 (2024-02-12)
Raised a ValueError in utils.next_scan_id when found highest id doesn’t start with scan_type parameter. [sgeulette]
0.8 (2024-02-12)
Improved utils.next_scan_id to check if found highest id starts well with scan_type parameter. [sgeulette]
Added gh actions for tests. [sgeulette]
0.7 (2022-10-28)
Corrected parameter typo in utils.next_scan_id and utils.scan_id_barcode. Added sphinx compliant doc strings. [sgeulette]
0.6 (2021-04-21)
In utils.highest_scan_id, avoid 2 return for lisibility. [gbastien]
0.5 (2019-09-24)
Skip empty scan_id in highest_scan_id method. [sgeulette]
0.4 (2018-01-22)
Corrected unused parameters in consume function. [sgeulette]
Corrected method not called => made a property. [sgeulette]
Handle several portal types in search. Take the first one for creation [sgeulette]
0.3 (2017-12-18)
Removed commit method that tried to manage retry of failing commits, queuing does not manage order, this will be managed another way when necessary. [gbastien]
Added method consume that is the default method called by consumers to consume a message using the create_or_update method. [gbastien]
0.2 (2017-11-27)
Added possibility to handle several portal_types in methods utils.highest_scan_id, utils.next_scan_id and utils.scan_id_barcode. [gbastien]
In utils.highest_scan_id, do the portal_catalog search unrestricted so we are sure that every elements are found. [gbastien]
Make it possible to use a different portal_type for query or creation. This is useful if consumer.file_portal_type returns several portal_types, we need to know which of the returned portal_types we need to use for file creation. [gbastien]
0.1 (2017-06-01)
Some improvements [sgeulette]
Initial release, inspired from imio.dms.amqp. [gbastien]
Metadata
Release files for imio.zamqp.core 0.13.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 |
|---|---|---|---|---|
| imio_zamqp_core-0.13.1.tar.gz | 21.4 kB | Without provenance | Details for imio_zamqp_core-0.13.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| imio_zamqp_core-0.13.1-py3-none-any.whl | Python 3 | none | any | Details for imio_zamqp_core-0.13.1-py3-none-any.whl |
Total release size: 35.3 kB
Release files / imio_zamqp_core-0.13.1.tar.gz
| Download URL | imio_zamqp_core-0.13.1.tar.gz |
|---|---|
| Size | 21.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c23c770e72f498acb02d48987fbaa3df275a4145b41d84a3c79747a375374379
|
|
BLAKE2b-256 checksum How to use checksums |
b0a83cd509767ecab6c7ccefb1e3383b65fb8cfbe628fcd804434d5e8e7ba5c4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.2
|
Release files / imio_zamqp_core-0.13.1-py3-none-any.whl
| Download URL | imio_zamqp_core-0.13.1-py3-none-any.whl |
|---|---|
| Size | 13.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6c76f8c45e8299fdf716706d64f5af98335c13e649b1b4c4701622d200965478
|
|
BLAKE2b-256 checksum How to use checksums |
0ea5ac1da107491cce8cc9ccdb0e9557b7e0ee66d6a972fd37e0d3fe0dd97254
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.2
|
Security for imio.zamqp.core 0.13.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.