bryl
Declaratively defining then:
constructing and
serializing
fixed sized records that are composed of:
typed
fixed sized
fields. This might look e.g. like:
import datetime
import bryl
class MyRecord(bryl.Record):
a = bryl.Alphanumeric(length=20)
b = bryl.Date('YYYYMMDD')
c = bryl.Numeric(length=10, align=bryl.Field.LEFT)
filler = bryl.Alphanumeric(length=10).reserved()
r = MyRecord(
a='hello',
b=datetime.datetime.utcnow().date(),
c=12312,
)
assert isinstance(r, dict)
print MyRecord.c.offset, MyRecord.c.length
assert MyRecord.load(r.dump()) == r
Some applications:
…
use
$ pip install bryl
dev
$ git clone git@github.com:balanced/bryl.git
$ cd bryl
$ mkvirtualenv bryl
(bryl)$ pip install -e .[tests]
(bryl)$ py.test
release
Now that all tests are passing:
Update bryl.__version__ to new {version}.
Commit that git commit -am "Release v{version}"
Tag it git tag -a v{version} -v v{version}
Push it git push origin --tags
and travis will take it from there.
Metadata
Release files for bryl 0.1.0
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 |
|---|---|---|---|---|
| bryl-0.1.0.tar.gz | 8.6 kB | Without provenance | Details for bryl-0.1.0.tar.gz |
Release files / bryl-0.1.0.tar.gz
| Download URL | bryl-0.1.0.tar.gz |
|---|---|
| Size | 8.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
586b474bbe997b0399cdb7228ad3bf2892b397cd93b2865b1755e9fba690921c
|
|
BLAKE2b-256 checksum How to use checksums |
6e86f18e4401d4bb7253154248410512d9283fe20b5b6ceced164b96f35af6d3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for bryl 0.1.0
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.