| Project | Versions |
|---|
acemq-amqp | 0.2.0, 0.3.0, 0.5.0, 0.6.0, 0.7.0, 0.7.1, 0.7.10, 0.7.11, 0.7.12, 0.7.2, 0.7.3, 0.7.4, 0.7.5, 0.7.6, 0.7.7, 0.7.8, 0.7.9 |
acemq-amqp-fastapi | 0.1.0, 0.1.1, 0.1.2, 0.1.3, 0.1.4, 0.1.5 |
Installing from it
pip install acemq-amqp --index-url https://acemq.org/pypi/simple/
To keep PyPI for everything else and take only AceMQ from here, use
--extra-index-url instead. Be aware of what that means:
pip merges the two indexes and picks the highest version it finds under
a name, whichever index it came from. Naming this index with
--index-url and pinning the version is the arrangement with
no surprises in it.
In a requirements file:
--extra-index-url https://acemq.org/pypi/simple/
acemq-amqp==0.2.0
Why this exists
The AceMQ Python library is not on PyPI yet. A project name there is
permanent and a released version cannot be re-uploaded — deleting it does
not free the filename — so the library is served from here until that
decision is one worth making irreversible.
Nothing about the package changes when it moves. The same
pip install acemq-amqp works from either index.
What a static index can and cannot do
| Capability | Here |
|---|
| Install and resolve dependencies | yes |
| Version listing | yes |
| Hash checking | yes — every link carries its sha256 |
| Search | no — there is no server to ask |
| Yank | no — delete the file and re-index |
| Ownership and signing | no — the repository is the record |
The index is PEP 503: a page per project listing its files, each link
carrying a #sha256= fragment that pip verifies before it
installs. That fragment is what makes the download trustworthy, so it is
part of the link rather than a checksum file beside it.
Elsewhere