A package to support resellers.
It maintains in a postgres database information about providers, products (called articles), clients, orders and deliveries. It uses a Zope2 frontend for user interaction.
It assumes a single (implicit) reseller and several “provider”s and “client”s.
Each provider provides “article”s which the clients can buy.
Clients buy articles in “unit”s; the provider provides them in “packet”s which contain an integral number of “unit”s. If the “packet_size” is different from 1, then the reseller repackages the delivered articles for its clients.
The reseller continously collects “client_order_item”s and periodically issues “order”s to a provider consisting of “provider_order_item”s.
The reseller occationally receives a “provider_delivery” for an order consisting of “provider_delivery_item”s and splits them into “client_delivery_item”s.
There is a special client, used as stock. It can be used to balance orders and deliveries. It (and it alone) can have negative “unit” values in its “client_delivery_items” - indicating that units have been taken out of the stock.
Usually, we do not delete items. Instead, we mark them as not “active”. This is in order not to break references.
1 maintainer
Metadata
1 maintainer
Release files for dm.zope.reseller 1.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 |
|---|---|---|---|---|
| dm.zope.reseller-1.1.tar.gz | 101.4 kB | Without provenance | Details for dm.zope.reseller-1.1.tar.gz |
Release files / dm.zope.reseller-1.1.tar.gz
| Download URL | dm.zope.reseller-1.1.tar.gz |
|---|---|
| Size | 101.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
01a95b7161c6406c5d7964e4e3b3e207112d92ec273d5b7a3ec8aa8ce966503f
|
|
BLAKE2b-256 checksum How to use checksums |
012c41c14429039c0c3cd1d50da12df14c83d9921730919f5a91199186a405da
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Python-urllib/2.7
|
Security for dm.zope.reseller 1.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.
