beancount-reds-plugins
A collection of plugins for Beancount, software for plain text, double entry bookkeeping. See README.md in individual directories for plugin specific documentation.
Plugin list:
- autoclose_tree: automatically closes all of an account's descendants when an account is closed.
- capital_gains_classifier: rebooks capital gains into separate long and short accounts, and separate gains and losses accounts
- effective_date: enables per-posting dates (each posting in a transaction can have a different date)
- opengroup: Inserts open statements for sets of accounts based on specifiable rules.
- rename_accounts: rename arbitrary accounts on the fly (eg: move Taxes from Expenses to Income when you temporarily want to view all your Expenses except taxes)
- zerosum: find matching pairs of postings that sum up to zero. Useful in de-duplication, and tracking things such as reimbursements, rebates, etc.
Installation
pip3 install beancount-reds-plugins
Or to install the bleeding edge version from git:
pip3 install git+https://github.com/redstreet/beancount_reds_plugins
Usage
Invoke and configure a plugin by including it in your beancount source. For example,
invoke the rename_accounts plugin like so:
plugin "beancount_reds_plugins.rename_accounts.rename_accounts" "{
'Expenses:Taxes' : 'Income:Taxes',
}"
See README.md in individual directories for how to configure each plugin.
Disabling plugins during the import process
In general, no plugins should run on the source files that are passed to
smart_importer. Here's an article
that shows how.
In short (this is for zsh, adapt to your shell as needed):
bean-extract my.import -f <(echo 'plugin "beancount.plugins.auto_accounts"'; cat ${INGEST_ROOT}/../source/*) $file
Metadata
Release files for beancount-reds-plugins 0.4.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 |
|---|---|---|---|---|
| beancount_reds_plugins-0.4.0.tar.gz | 53.2 kB | Without provenance | Details for beancount_reds_plugins-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| beancount_reds_plugins-0.4.0-py3-none-any.whl | Python 3 | none | any | Details for beancount_reds_plugins-0.4.0-py3-none-any.whl |
Total release size: 108.3 kB
Release files / beancount_reds_plugins-0.4.0.tar.gz
| Download URL | beancount_reds_plugins-0.4.0.tar.gz |
|---|---|
| Size | 53.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
33ed652d9d08c6c1de472900d92a7695f6b5f864c3ad23812acd68e756ed0565
|
|
BLAKE2b-256 checksum How to use checksums |
679348ef31e6c6ed5f09896947a0b40eaf2ad69d15b9a9687b6a94596aa9a249
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.5
|
Release files / beancount_reds_plugins-0.4.0-py3-none-any.whl
| Download URL | beancount_reds_plugins-0.4.0-py3-none-any.whl |
|---|---|
| Size | 55.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
186d4d625dcd094043b489f942d44b8cb603a2d5710083e0ce2ea56c2dd133fa
|
|
BLAKE2b-256 checksum How to use checksums |
55ab307c9b30229f6e75fcad14008e06291d93452b577ebd50412c1f30c0df49
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.5
|
Security for beancount-reds-plugins 0.4.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.