This is Python a port of barby library written in Ruby. I couldn’t find lightweight Python barcode generation library of the same caliber as barby (elaphe is broken and others don’t support GS1-128 and QRCode at the same time, so I ported barby).
API is basicly the same as of barby, but in Python style.
The port is very quick and not complete at the moment (I ported only parts I really need for my project), I will port the rest eventually.
Also the port is quite direct, in a sense there are a lot of places in Python code which have more Rubyish flavour instead of Pythonian (e.g. a lot of @property decorators to call methods without parenthesis). I did it to avoid logic errors during porting process, I will make code more Pythonian in the future.
See also:
[barby]: http://toreto.re/barby/ [elaphe]: http://code.google.com/p/elaphe/
1 maintainer
Metadata
1 maintainer
Release files for cfc-barpy 0.1.3
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 | |
|---|---|---|---|---|
| cfc-barpy-0.1.3.tar.gz | 9.4 kB | Without provenance | Details |
Release files / cfc-barpy-0.1.3.tar.gz
| Download URL | cfc-barpy-0.1.3.tar.gz |
|---|---|
| Size | 9.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bbbd452509e521116d150b8eaec4fe0d405f47aec99cbf18f93c3bab2ce98903
|
|
BLAKE2b-256 checksum How to use checksums |
ad6d3db2a9939e82030edd15c33f16455b4e7857a285c86026f3dce4c2c1877a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for cfc-barpy 0.1.3
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.
