nacha
NACHA is a fixed sized record format used to represent financial transactions composed like this:
FileHeader
CompanyBatchHeader
EntryDetail
EntryDetailAddendum
...
...
CompanyBatchControl
...
FileControl
which we express using bryl. Writing is done like this:
with open('sample.nacha', 'w') as fo:
writer = nacha.Writer(fo)
with writer.begin_file(
...
):
with writer.begin_company_batch(
...
):
writer.entry(...):
...
...
Reading is done by iterating records like this:
with open('sample.nacha', 'r') as fo:
reader = Reader(fo, include_terminal=True)
for record, terminal in reader:
...
Or structured like this:
with open('sample.nacha', 'r') as fo:
reader = Reader(fo)
reader.file_header()
for company_batch_header in reader.company_batches():
for entry_detail, entry_addenda in reader.entries():
...
reader.company_batch_control()
reader.file_control()
use
$ pip install py-nacha
dev
$ git clone git@github.com:DisruptiveLabs/nacha.git
$ cd nacha
$ mkvirtualenv nacha
(nacha)$ pip install -e .[tests]
(nacha)$ py.test tests.py --cov=nacha --cov-report term-missing
release
Now that all tests are passing:
Update nacha.__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 py-nacha 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 | Actions |
|---|---|---|---|---|
| py-nacha-0.1.3.tar.gz | 7.5 kB | Without provenance | Details for py-nacha-0.1.3.tar.gz |
Release files / py-nacha-0.1.3.tar.gz
| Download URL | py-nacha-0.1.3.tar.gz |
|---|---|
| Size | 7.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
96bf98ecc1af3ebb268f6123b7d7d33752e1f2e27e8701fe2e38ff461cab8720
|
|
BLAKE2b-256 checksum How to use checksums |
b8a7f787a26191cc8beb4eb4111f6d5fbc0e7bd90ba2ca4e41d912ba2cb55156
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for py-nacha 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.